Custom chatbot implementation fees must fund engineering effort and project purchases; they do not automatically create subscription income. Fictional Beacon Dialog sells 176 engineer hours from 320 scheduled hours per base month. Maintenance is part of that same pool, and client production usage is outside the chosen fees.

THE IDEA TO KEEP

Validate effort to acceptance and the payer for ongoing usage before committing implementation or maintenance capacity.

Keep implementation revenue separate from a hosted product

Beacon Dialog is a Dallas-Fort Worth hybrid studio for business sponsors with an approved use case, usable content and system access. Discovery, chatbot build, integration, evaluation and maintenance allocate one paid principal-and-engineer calendar. There is no assumed subscriber base or recurring platform margin. The fictional forecast covers January 2027 to December 2029.

The scope needs an input-readiness point, an agreed deliverable, evaluation work, review and handover. Integration changes or weak source material can expand effort without creating another implementation fee. Client production hosting, usage and platform charges require a separately defined budget if the studio is to pay them.

Allocate development and maintenance hours once

The selected base mix produces $35,024.00 at a weighted $199.00 per sold engineer hour and 55% utilization. Maintenance hours in the table cannot also be sold as new-build time. The fictional figures exclude the opening ramp and later growth.

Beacon Dialog: base month; shared engineer hours and USD, with no subscription receipts.
ServiceBase sold volumeFee per hourBase revenue
Discovery26.4 hour$200.00$5,280.00
Chatbot build61.6 hour$210.00$12,936.00
Integrations44 hour$210.00$9,240.00
AI evaluation26.4 hour$180.00$4,752.00
Maintenance17.6 hour$160.00$2,816.00
Total selected mix176 hour$199.00 weighted$35,024.00
Base engineering fees versus the paid studio: Sold workload 176 hours/month; Base fees $35,024.00/month; Contribution 91%; Base EBITDA -$449.00/month
Checked scenario explanation; the text and table provide the same values and limits.

Separate development purchases from production obligations

Development API/compute and outside QA/security review are budgeted at 5% of revenue. That ratio is a scenario allowance, not a current provider quote. Production usage by the client is excluded unless newly scoped. Neither purchased review nor cloud use creates an extra engineer.

The principal is already a paid delivery role. Quarter-time operations coordinates projects and invoices without adding technical capacity. Internal engineering software, office, training and professional cover remain recurring overhead. Define who owns post-handover changes before reserving more maintenance time.

An annual improvement does not mean opening cash is effortless

The saved opening year forecasts $385,264.00 revenue, -$37,259.84 EBITDA and -$40,459.84 net income. EBITDA excludes depreciation, interest and income tax. The final forecast year has $35,625.60 EBITDA, but the case does not recover startup uses within its horizon.

The assumed 45-day collection leaves $52,536.00 receivable at the end of the opening year. Proposed equity is $170,000.00, including $100,000.00 owner capital; it is uncommitted. Launch uses total $18,600.00. No debt or physical inventory is modeled, and refundable office deposits are excluded.

Test paid implementation effort through acceptance

Log discovery, build, integration fixes, evaluation, client review and handover against the accepted fee. Record development purchases separately from the client's production costs and from internal software overhead.

If support requests crowd out new delivery, revise the retained scope and calendar before describing maintenance as a scalable recurring product. Use collected implementation contribution to judge the next commitment, without promising a particular AI outcome.

Make the next decision with your own evidence

Measure engineering and review effort to acceptance, development purchases, client production responsibilities and payment dates on a defined paid implementation.

Explore published business plan examples ↗

Create my own business plan ↗

About the worked case

Beacon Dialog is a fictional prelaunch scenario prepared with AI assistance. Inputs are illustrative; forecast results come from the matching saved financial model. Funding is proposed. The diagrams explain the case and do not depict actual premises, established demand or promised earnings. Replace the assumptions with evidence before committing.

Read our methodology
Continue exploringBack to the journal ↗