Start with the job, not the AI label
Business automation can mean a single form-to-CRM handoff or a much wider operational system. Those projects should not receive the same quote. Start by describing the trigger, the people involved, the tools, and the action that should happen next. Add the exceptions: missing information, duplicate records, a tool being unavailable, or a conversation that needs a person. A clear process makes it possible to separate a useful first release from later ideas. The figures below describe Puzinski’s own starting offers, not an industry average or a price for every business.
A focused handoff starts at $1,250
The Lead Handoff Sprint connects one inquiry source to an existing CRM, applies one assignment rule, and adds one notification or follow-up. It includes test cases, a walkthrough, and handover notes. It assumes working accounts, appropriate access, and an agreed process. This is a practical starting point when the main problem is that a new inquiry needs to reach the right person. It does not include a full conversational AI agent, a database migration, or every messaging channel. Those needs change the scope.
A wider workflow starts at $3,000
The Operations & AI starting scope covers one workflow across up to three existing tools, one trigger, and up to five agreed actions. It includes a process map, implementation, test scenarios, exception handling, documentation, and a team walkthrough. AI assistance can be part of that workflow when useful; a deterministic rule may be enough for other steps. The important distinction is the work performed and how it is checked. Multiple independent workflows, complex agents, and migrations receive a tailored quote.
What makes the quote larger?
More systems create more dependencies to understand and test. Other drivers include incomplete data, multiple user roles, approval rules, complex permissions, conversation handling, a custom dashboard, and unusual exceptions. Existing documentation and usable APIs can make a meaningful difference. If the process needs its own workspace rather than connections between current tools, a focused web app may be a better approach. Puzinski’s Custom Business App begins at $7,500 for the limited first-release scope on the packages page; larger or native mobile products are assessed separately.
Separate the build from running costs
A project fee pays for the agreed implementation. CRM subscriptions, messaging charges, hosting, AI/API usage, and other third-party costs are separate. Request a clear list of expected dependencies and identify who owns each account. Also agree on ongoing monitoring, change requests, issue triage, and the response window. Routine care and a new feature are different obligations. An inexpensive first integration can still need maintenance when a connected platform changes its behavior.
Define success before implementation
Choose an observable acceptance condition: the right CRM fields are created, an owner receives the task, a follow-up appears, or a reviewer can inspect the action. Use representative examples and test both successful and incomplete requests. Establish how a person notices and resolves exceptions. Avoid assuming that faster routing automatically proves higher revenue. If financial impact matters, agree on the baseline, reporting definitions, and observation period so the business can assess what actually changed.
Prepare a brief that can be quoted
Share the recurring task, its approximate frequency, current tools, process owner, desired first outcome, and the most common exception. Say whether there is an existing workflow or a new build, and identify any timing constraints. A high-level description is enough for an initial inquiry; do not send private customer records, passwords, or confidential documents. The next step is a scoped proposal with deliverables, dependencies, timing, fees, and support expectations.