When custom work is the right answer — and when it is not
Most service businesses should start with a package. Starter, Pro, and Authority already cover the common path: answer the call, capture the lead, qualify it, book the appointment, and follow up. Custom work makes sense when the business has a constraint the packages cannot express — multiple locations with different routing rules, a dispatch system that requires a private integration, a qualification tree that changes by contract or property type, or a handoff process that has to match an existing SLA.
A custom engagement starts with a discovery call, not a build. We document the current intake path, the systems involved, the places where the process breaks, and the outcome the business wants. From that we write a workflow design: the decision tree, the data handoffs, the escalation rules, and the exceptions that must stay with a person. The design is reviewed before any configuration or code is written, because most custom projects fail at the boundary between what the software can do and what the operation actually needs.
The build connects the approved workflow to the tools that already hold the data. That may mean a CRM, a scheduling platform, a dispatch system, a billing tool, or a webhook into something internal. Every integration is tested with recorded calls and a small pilot group before launch. The launch is monitored, and the first weeks are used to refine the routing based on real conversations rather than assumptions from the discovery call. The software remains month-to-month; the custom setup is a one-time scoping and build fee.
Custom is not the right choice when the request is really a package feature in disguise. If the business needs missed-call text-back, standard qualification, or calendar booking, a package will usually be faster and less expensive. It is also not a way to avoid defining the process. A custom workflow still needs an owner, approved scripts, escalation contacts, and a measurement plan. The build can be bespoke; the operating discipline cannot.
Package vs. custom engagement
| Custom engagement | Standard package | |
|---|---|---|
| Best for | Multi-location routing, private integrations, complex eligibility rules | Missed-call recovery, qualification, booking, follow-up |
| Timeline | Typically 2–4 weeks after scoping | Most builds target 48–72 hours after onboarding |
| Scope | Documented workflow design plus a one-time build fee | Defined plan inclusions, month-to-month |
| Integration | Private or non-standard systems, reviewed case by case | Supported calendar, CRM, and messaging tools |