Engagement model Three stages, one team

Quoted to the
work. Not a rate card.

A published price is either too high for the small jobs or too low for the real ones. We quote after a 30-minute discovery call, in writing, with the scope attached. Most engagements move through three stages: Audit, Build, Retainer.

How we engageAudit → Build → Retainer
01
Stage one

Audit.

A paid one to two week discovery. We walk your business, identify five to ten high-impact opportunities, and deliver a prioritised roadmap with effort estimates. Most builds start here.

  • Stakeholder interviews and process mapping
  • Shadow sessions with the people doing the work
  • Prioritised opportunity roadmap with ROI estimates
  • Effort estimates per opportunity (S, M, L, XL)
  • Build-ready scope for the top three opportunities
Fixed scope One to two weeks

About one in five audits ends with "don't build it, here's why." We think that's healthy. You own the roadmap either way.

02
Stage two

Scoped build.

Fixed-scope, fixed-price delivery against the roadmap. You pick which opportunities to build. We scope, quote, sign, and ship. No retainer commitment, no hourly billing.

  • Written scope: deliverables, milestones, dependencies
  • Fixed price in ZAR (or USD/EUR for international)
  • 50% on signature, 50% on acceptance
  • Weekly check-ins and a Notion or Linear board you can see
  • Code lives in your repo from day one
Timeline Two weeks to four months

If our estimate is off, that's on us. If new scope appears, we surface it the same day in writing and you decide whether to add it.

03
Stage three (optional)

Retainer.

Once a system is live, you can keep us on a monthly retainer for evals, improvements, on-call response, and quarterly roadmap reviews. Retainer is opt-in. No system we ship requires us.

  • Eval harness maintenance and drift monitoring
  • Same-business-day response on production issues
  • Continuous improvements against agreed KPIs
  • Quarterly roadmap and ROI review
  • Capped monthly hours with rollover
Commitment Month to month, 30 days notice

Roughly half our build clients keep a retainer. The other half take the code, train internally, and tag us in when something breaks. Both are fine.

Why no rate card

A two-week internal tool and a six-month compliance system are not the same product. Publishing a single range either scares off the small projects or undersells the real ones. We'd rather skip the theatre and quote you the actual number, in writing, after a 30-minute call.

What every engagement includesAnd what it never does
Always included
  • Written scope before any work starts
  • Fixed price in your preferred currency (ZAR, USD, EUR)
  • All code in your repo, your cloud, your accounts
  • Weekly progress check-in
  • Eval harness for any AI component we ship
  • Plain-English handover for non-technical stakeholders
  • Two weeks of post-launch support on every build
Never included
  • Hourly billing or padded timesheets
  • Platform lock-in. We don't sell a SaaS pretending to be a service
  • "Discovery workshops" we charge for that produce a deck and nothing else
  • Equity-only or pre-revenue arrangements
  • Vapourware AI features that don't survive an eval
  • Reskinned ChatGPT wrappers sold as custom builds
FAQThings people actually ask
Why don't you publish prices?

Because every engagement is different and a published number is either too high for the small jobs or too low for the real ones. We quote after a 30-minute discovery call, in writing, with the scope attached. You never get a number without the work it covers, and we never get cornered into pretending two unlike projects cost the same.

How do you scope a project?

Most engagements start with a paid AI Audit. One to two weeks of structured discovery: interviews, process mapping, shadow sessions. We deliver a prioritised roadmap, real effort estimates, and a build-ready scope for the top three opportunities. From there you choose what to build, with us or with anyone else.

Why not hourly billing?

Hourly billing aligns nobody. It punishes us for being fast and punishes you for changing your mind. Fixed scope, fixed price, fixed deadline: that's the only way both sides care about the same outcome.

How do I know which service I need?

You usually don't, and that's fine. Start with the Audit. About one in five audits ends with "don't build it, here's why." That's healthy. You leave with a roadmap either way.

Do you work with startups?

Yes, if you have real revenue (or real funding), a specific workflow problem, and a budget that matches the scope. We're not a fit for pre-product or equity-only work. We've tried both and it doesn't work for anyone.

Do you work outside South Africa?

Yes. Joburg-based, working remote in UTC±5. We bill in ZAR by default and can invoice in USD or EUR for international clients. If you're east of Singapore the timezone math gets annoying; we'll be upfront about cadence.

Can we own the code?

Yes. All code is yours from day one. No platform fees, no licensing trap. The project repo lives in your organisation. You can fire us next week and the system keeps running.

What happens if the project goes over scope?

If it's our miss, we eat it. If new scope appears, we surface it the same day, scope it in writing, and you decide whether to add it. We'd rather lose margin than lose trust.

How fast can you start?

We're currently booking Q3 and Q4 2026 engagements. Discovery calls happen within a week of first contact. Builds typically kick off two to four weeks after a signed scope.

Want a real number?

Book a call. Get a
written quote within a week.

No deck. No charged "discovery workshop." A 30-minute call, then a one-page scope with a fixed price.

Book a discovery call See process