Services

Diagnosis first. Everything after it is smaller, faster, and aimed at what's actually broken.

Every engagement starts with evidence, not an opinion about your product. What follows depends on what the audit finds, not on which service was pitched hardest.

Ordered from first diagnosis to ongoing direction. Not sure which fits? Start with a systems diagnosis and we'll scope from there.

01

Systems Diagnosis

Starts with a Verifux audit of your live product.

Engagements from R40,000

Teams facing a high-stakes product decision, a rebuild, or a plateau, who want evidence before committing budget.

  • A full Verifux audit across MX, BX and AIX, 54 checkpoints spanning 9 pillars, plus an optional DX craft score
  • A structured report ranking what's actually broken by cost, not by opinion
  • A working session to walk through the findings and what they mean for your roadmap
Book a systems diagnosis
02

Diagnosis-Led Redesign

Starts with your diagnosis findings, ours or an existing audit.

Scoped to the audit findings, typically R60,000 to R150,000

Teams who already know what's broken, from a diagnosis with us or elsewhere, and need it fixed.

  • Design work scoped to what the audit found, not a wholesale visual refresh
  • Behavioural science and systems thinking applied to the specific leverage points
  • A smaller fix shipped and instrumented before a bigger bet gets made
Talk it through
03

AI Product Strategy

Starts with an AIX pass of the Verifux audit.

Scoped in conversation

Teams that need their product legible to AI agents and ready for an AI-native market, not marketing that only claims to use AI.

  • An AIX-focused audit: structured data, semantic HTML, llms.txt, agent-actionable interfaces
  • A read on how AI surfaces and answer engines currently treat your product
  • A prioritised plan for where AI is real leverage in your build process, not just your product's surface
Talk it through
04

Fractional Product Direction

Starts with a scoping conversation on cadence and focus.

Scoped in conversation

Teams that need diagnostic judgment applied continuously, not once.

  • Embedded product direction from one senior practitioner, not a team of juniors
  • Ongoing diagnosis as the product and market change, not a single point-in-time report
  • Direct accountability for outcomes, not a deliverables checklist
Talk it through
05

MVP Validation

Starts with a conversation about what's already validated and what isn't.

Scoped in conversation

Funded founders about to build, who want the idea validated against evidence before a line of code gets written.

  • A lighter-weight diagnosis scoped to a pre-launch product or prototype
  • The riskiest assumption identified, and the cheapest way to test it before building
  • A build-ready brief for engineering
Talk it through

Not sure which one

Start with a conversation, not a proposal.

Tell me what isn't working. I'll tell you honestly whether a diagnosis is the right first step, or whether something else is.