Resources / tools

Models you can actually use.

Six small calculators turn open questions about scope, capacity and growth economics into explicit assumptions. They are planning tools, not forecasts.

Use the estimates well

Choose a decision, then a calculator.

Use consultation capacity to compare session availability with likely demand; hotline revenue to model paid minutes; marketplace revenue to see the platform share; Google Ads ROAS to compare gross client value with ad spend; content production to estimate workload; and website scope to compare build complexity.

None of these tools imports a market benchmark or predicts demand. Change the assumptions to fit your operation and run low, expected and high cases. If a result looks attractive, check the underlying capacity, refund behavior, staff time and customer quality before spending.

For a proposal, bring the assumptions and what you can verify. The outputs are planning aids, not quotes, financial advice or guaranteed returns.

Discuss the operating model ↗

Decision guide

Read the output before making a budget decision.

A capacity estimate is not demand. A hotline or marketplace revenue estimate is not cash left after reader payments, refunds, telecom and support. The advertising calculator shows gross return on ad spend, not profit or accounting ROI.

The website scope score compares relative complexity; it is not a price quote. The content planner counts production volume and writing cost, while editing, expert review and distribution may need separate effort.

Use observed business numbers where you have them, then change the weakest assumption. That gives you a specific question to test before investing in a larger build or campaign.

Practical detail

Try a sensitivity check

Run a conservative, base and optimistic version of a calculator by changing one uncertain input at a time. For a hotline, compare connected minutes per available reader hour. For advertising, compare qualified enquiry rate and close rate separately. For a website scope, distinguish a simple service site from integrations and complex roles.

Write down where each input came from and revisit the model with actual results after launch. A tool is most valuable when it shows which assumption matters and which decision to test next.