Assessment, prototype, implementation, and defined care - scoped around a visible problem, a named owner, ordinary business information, and a measurable acceptance gate.
01
Advise
Practical Systems Assessment
$450–$1,200 example range
One bounded workflow or public-facing customer journey
Included
Current-state map and evidence gaps
Opportunity scorecard and risk classification
Vendor shortlist or build-versus-buy recommendation
ROI assumptions and smallest useful next step
Not included
Implementation or vendor subscription cost
Legal, privacy, cybersecurity, or regulated-data assurance
02
Build
Workflow Prototype
$1,200–$3,500 example range
One browser prototype using synthetic or approved non-sensitive data
Included
Interactive proof of the proposed workflow
Approved-information and human-handoff controls
Responsive and accessibility testing
Acceptance criteria and implementation decision brief
Not included
Production messaging, payments, or customer-data migration
Unlimited revisions or custom platform replacement
03
Implement
Controlled Implementation
$2,500–$7,500 example range
One approved workflow using client-controlled accounts
Included
Configuration, documented integrations, and permissions
Acceptance testing, training, SOP, and fallback
Launch checklist and 30-day review
Handoff with named owners and maintenance plan
Not included
Regulated or highly sensitive data
Ongoing support beyond the written period
04
Maintain
Defined Care Plan
$175–$650 example monthly range
Specific monitoring, content, and improvement responsibilities
Included
Scheduled checks and a bounded update allowance
Knowledge and workflow review
Monthly issue and change summary
Not included
24/7 support, incident-response guarantee, or unbounded development
Third-party subscription and usage charges
Pricing assumptions
What keeps the range bounded.
Client provides one decision owner and timely review.
Work stays within one written workflow and ordinary business information.
Client owns production accounts, billing, domains, and vendor contracts.
Third-party fees, taxes, paid media, hardware, and data cleanup are separate.
Material scope changes require a written change decision before work continues.
Client responsibilities
Authority stays with the owner.
Supply accurate services, policies, hours, prices, and operating rules.
Approve customer-facing content and exception handling.
Provide test accounts and least-privilege access where implementation is approved.
Name a primary operator, backup, knowledge owner, and final approver.
Review legal, privacy, employment, marketing, and industry obligations with qualified counsel.
Optional add-ons
Added only by written decision.
Additional workflow mapping
Vendor trial facilitation
Content migration from approved sources
Staff scenario training
Additional acceptance-test cycle
Printable operating manual
Qualification
A good fit has a process owner and a safe boundary.
Initial fit
A visible workflow problem with a named owner
Public or ordinary business information
A testable outcome such as response time, completeness, or staff effort
Willingness to start with a bounded pilot and human review
Not an initial fit
Medical, legal, tax, lending, credit, insurance, identity, or financial-data workflows
Payment-card custody, background checks, surveillance, or employee scoring
Autonomous commitments, cold-message automation, or misleading synthetic proof
Projects requiring unsupported guarantees, credentials, or invented results
Common questions
Boundaries before promises.
Do you replace an existing CRM or scheduling platform?
Usually no. The default is to improve the process and configure a suitable system of record before considering custom software.
Will AI speak to customers on its own?
Not by default. Approved-source answers, visible confidence, stop rules, and human handoff come first. Any later authority requires explicit written scope and testing.
Are the price ranges fixed?
No. They are examples for planning. A real price follows discovery, vendor checks, data review, responsibilities, and acceptance criteria.
Who owns the accounts and data?
The client should control production accounts, vendor contracts, exports, permissions, and offboarding.
Conversation notes
Objections are discovery inputs.
We already have software.
Good. The first question is whether the current process, configuration, ownership, or training is the real constraint.
Can we automate everything?
Only after the workflow, exceptions, data, permissions, failure modes, and authority boundaries are proven. Smaller authority is usually safer and easier to measure.
Can you guarantee revenue?
No. The work can measure process and customer-path changes; revenue attribution depends on factors outside the system.