CRM & Lead Management

Those are full CRM platforms — broad, configurable, and powerful for businesses willing to invest in setup, training, and ongoing administration. Starter CRM is a lightweight lead pipeline configured around one outcome — stop losing leads and know what to follow up on next. We may use an existing CRM, a lightweight database, or a custom pipeline depending on your needs and what's already working. We're not trying to replace enterprise CRM in the Starter package.

Yes, if it's usable and has the fields, access, and integration options we need. If your existing CRM is broken, overbuilt, or already ignored by your team, we'll tell you before building on top of it — that's a sign you need cleanup or migration, which belongs in Pro or Custom. If your CRM blocks API access, charges separately for required integrations, lacks fields we need, or otherwise can't support the workflow at your current plan, we may recommend a lightweight pipeline or Pro CRM instead.

It depends on your situation. For teams without an existing CRM, we typically deploy on a lightweight database (Airtable, Postgres, or similar) so you don't take on a new seat-based subscription on day one. For teams with an existing CRM that's working, we configure within your CRM. We confirm the right approach during the Free Scan call.

One intake source is one primary place leads enter the system — a website form, a shared inbox, a calendar booking form, a phone-call summary feed, or a spreadsheet import. If your leads enter through more than one channel, that's a Pro engagement.

Starter is focused on new leads going forward. Historical imports, deduplication, field cleanup, or migration from another CRM belong in Pro or Custom — that's discovery-sprint work, not a Starter add-on.

Yes, based on rules you approve during the build. Common rules — lead replies to first email → move to Engaged; no reply for 7 days → move to Stalled; demo booked → move to Qualified. We don't deploy automatic stage advancement without you signing off on the rules first — getting the rules wrong is how teams stop trusting the pipeline.

For email, Starter can include simple alerts or reminders tied to the approved pipeline rules. Auto-replies, multi-step follow-up sequences, and sales-nurture campaigns may require Pro CRM or Automation Buildout depending on scope. For text messaging, we scope carefully because consent, opt-out handling, vendor setup, and TCPA considerations matter. Outbound SMS at scale belongs in Pro or Custom.

Starter includes basic deduplication rules (same email or same phone within 30 days = treated as the same lead). Aggressive dedup across multiple sources, fuzzy name matching, or historical cleanup belongs in Pro or Custom.

Your business owns the lead data. Wherever possible, the CRM, database, calendar, and notification tools are set up under accounts you control — so when an engagement ends, you keep operational access without relying on KV Intelligence.

Typical software/usage runs $50–$300/month depending on which CRM we deploy on, your team size, email volume, automation volume, and reporting needs. We don't mark up software or take vendor commissions — you're billed directly by the vendor wherever possible.

Sometimes, but it must be scoped carefully. Workflows touching healthcare-adjacent, legal-adjacent, financial-adjacent, employee, or otherwise regulated data may require Pro or Custom because access control, logging, and retention requirements are higher.

Starter includes basic error alerts for expected failure points — intake source down, stage rule failed to fire, daily summary didn't generate. After the 30-day tuning window, vendor changes or new failure modes are covered under a monthly Care Plan or quoted separately.

Yes. Every deployment includes a documented kill-switch path so you can pause automation during outages, reorganizations, holidays, or any time you need manual control. Recovery is documented in the handoff materials.

We'll tell you before launch. Starter assumes a defined sales process with clear stages and follow-up rules. If your stages are unclear, your team disagrees on what "qualified" means, or your follow-up rules are improvised, we'll recommend cleanup or a Pro engagement before building automation on top — automating a confused process just creates a faster confused process.

Marco and Felix are the names we use for the CRM agents running our own business — Marco handles pipeline queries and lead lookup, Felix handles stage-move actions and follow-up scheduling. The names you see in a sales call demo are our internal agents. Your deployment uses whatever naming and personality conventions fit your business.