Frequently asked questions.

A solo studio. The person you talk to on the discovery call is the person writing the code and shipping the system. That's the entire pitch. When the work needs more capacity than one engineer, I bring in trusted contractors I've worked with before, not subcontracted strangers.

Multi-location operations with real revenue and real operational drag. Industry-agnostic. Education, franchises, professional services, real estate, gaming, entertainment. The signal is operational complexity. Five or more tools, manual handoffs between systems, leads or customers leaking out of the gaps.

Solo operators with simple workflows that a no-code tool already covers. Pre-revenue startups looking for free spec work. Anyone wanting a strategy deck without a build at the end of it. If your operation isn't generating enough revenue to justify a $6K floor, the right answer is probably to wait.

Engagements start at $6,000. The standard Operations Overhaul ranges from $12,000 to $18,000 for a single location. Multi-location rollouts scale from there. Retainers after the initial engagement run $2,000 to $3,200 per month. All contracts are paid upfront before each month.

The standard Operations Overhaul is six weeks. Week 1 is the audit. Week 2 is architecture. Weeks 3 to 5 are build, integration, and pilot deployment. Week 6 is optimisation, training, and handover. Multi-location rollouts add 1 to 2 weeks per additional location depending on complexity.

For existing clients only, at $117.50/hour for small additions outside the standard engagement. New work is fixed-price. The reason is simple. Hourly rates incentivise the wrong things. Fixed price means you know what you're paying and I'm motivated to ship the right thing as fast as possible.

45 minutes. No pitch. We map your current operations, identify the highest-leverage problem, and decide together whether the Operations Overhaul is the right shape. By the end of the call you'll know what to fix first and whether I'm the right person to help.

Sprint-based with a clear definition of done at every stage. Weekly check-ins, async updates between calls, full visibility into what's shipping and when. There are no surprises in the middle and there is no scope creep at the end. The schedule is the product.

Yes. The system, the code, the documentation, the playbook, the credentials. All yours. There is no proprietary Formaum platform you're renting. The work is yours from day one. If you take it and run it yourself after week 6, that's also fine.

Pilot-first, always. We launch at one location, watch it for a full week against real production data, fix anything that surfaces, and only then roll to the rest. Pilot-first is the difference between a launch and a recall. Multi-location is sold upfront as a phased plan, not a surprise add-on.

Claude (Anthropic) for AI. Claude Code for engineering. Trigger.dev, n8n, and Make for orchestration. Supabase, PostgreSQL, BigQuery for data. GoHighLevel, HubSpot, Salesforce, Pipedrive, Monday for CRM. Twilio, Vapi, ElevenLabs for voice. Next.js, FastAPI, Python for custom apps. The right tool for the job, not the one I happen to know best.

Production-grade AI agents have guardrails, observability, and graceful degradation built in. Every action is logged. Confidence thresholds route low-confidence decisions to human review. The system fails to a safe state when a model is unavailable. The difference between a demo and a production system is exactly this layer of boring infrastructure.

Claude is the default because of the model quality, the tooling around Claude Code and Skills, and the data privacy posture on Team and Enterprise plans. Where another model is the right tool (OpenAI for embeddings, Gemini for visual review, etc.) it gets used. Tool selection is per-job, not per-vendor.

Yes. NDAs are standard before any client material is shared. AI providers used (Claude, OpenAI, etc.) are on Team or Enterprise plans where applicable, meaning client data is not used for model training. Production credentials are stored in secrets managers, not hardcoded. Audit logs cover every agent action in production.

Yes. Most engagements are remote and I work with operations teams across Canada, the US, and the UK. Time-zone overlap is built into the sprint cadence. Geography is not a constraint.

Selected work is on the Case Studies page. Names are withheld under NDA. Numbers and architectures are real. If a buyer needs deeper specificity to make a decision, I'll arrange a reference call with a previous client where appropriate.