The Discovery Engagement

2–3 weeks · $5,000–$12,000 · Fixed fee

Every Rational Boxes engagement begins here. We spend two to three weeks inside your practice — mapping how the work actually gets done, writing down the judgment that makes it yours, and coming back with a costed plan for the first platform.

It is a working audit, not a sales process. You keep everything it produces whether or not a build follows.

Start with a Discovery

Why every engagement starts here

An $80,000 opening ask is too large for a first conversation. At that point neither side knows enough. You do not know whether we can hold your subject matter. We do not know whether the judgment behind your work can be encoded, or whether the demand you feel is real enough to build on.

The Discovery answers both questions for a fraction of what guessing wrong costs. We map how your practice actually runs, document the method underneath it, and hand back an architecture, a product concept, and a fixed-fee proposal you can act on with us or with any other team.

Most of what it produces is useful the week we find it, long before a line of code is written.

What the two to three weeks cover

Phase 1 — Process review and audit

Week 1. We walk every recurring process end to end, as it is actually performed rather than as it is documented.

  • A map of the real workflow, workarounds included
  • Where your hours actually go across a typical week and a typical engagement
  • Friction points — handoffs, waiting states, rework loops, approval bottlenecks — ranked with a cost estimate for each
  • Manual repetition: what gets reformatted, re-entered, re-explained, and re-calculated by hand
  • Every piece of information handled more than once, traced across tools, documents, and email
  • Tools, file stores, and subscriptions, with the overlap and the orphaned data named
  • What answering "where are we?" costs you in a month
  • Every point where work queues on you personally

The bottleneck map is the core input to build scope. It defines exactly what a platform would have to absorb.

Phase 2 — Methodology extraction

Weeks 1–2. Structured interviews that pull the consistent logic out from under your judgment.

  • Your methodology, documented — the intellectual property that currently exists only in your head
  • How you evaluate, score, compare, or diagnose, including the exceptions that break the rules
  • An honest line between what can be encoded and what genuinely still needs you, live
  • An inventory of the frameworks, checklists, and models you already have, each rated for encoding readiness
  • Who pays you today, who asks for access you cannot give, and where you are turning demand away

This one is worth having on its own. A documented methodology is what makes training, delegation, and succession possible, with or without software.

Phase 3 — Architecture and product concept

Weeks 2–3. We match the method and your real constraints to a stack lean enough to run profitably from the first subscriber.

  • Technical architecture recommendation, with hosting costs estimated up front
  • Product concept: the surfaces, the users, the subscription model, the feature scope
  • A fixed-fee build proposal with timeline, phases, and ownership terms, ready to sign
  • A written go / no-go recommendation

Nothing here gets re-discovered or re-billed later. If we build, these documents are the build.

The quick-win report

Phase 1 is consolidated into a ranked list of fixes you can make now, without waiting for anything to be built. It is designed to recover more in hours than the Discovery costs.

  • Most experts discover that 20–40% of their time goes to work far below their billing rate
  • Several friction points usually turn out to be fixable within days
  • The top repetitive tasks are often templatable this week, with no custom software at all
  • Redundant subscriptions and consolidation savings tend to surface on the spot
  • Status churn is a hidden tax, and a simple shared tracker usually cuts it long before a platform exists

This is what makes the Discovery a fair purchase rather than a gateway to a sales pitch. It pays back whether or not we go further.

What you walk away with

  • A process audit with a ranked quick-win report you can act on immediately
  • Your methodology and decision logic, documented and yours
  • An inventory of the knowledge artifacts you already have, rated for encoding readiness
  • Evidence of who actually wants what you do, and where demand is going unmet
  • A technical architecture recommendation with hosting costs estimated
  • A product concept document with feature scope
  • A fixed-fee build proposal with timeline, phases, and ownership terms
  • An honest go / no-go recommendation

2–3 weeks. $5,000 to $12,000, fixed. Where you land in that range depends on how many distinct processes are in scope and whether the sessions run on site or remote. The fee is agreed before we start and does not move.

You own all of it outright — the documents, the methodology map, and anything built later. That does not change.

What happens next

If the recommendation is go and both sides agree, the Discovery deliverables become the foundation of the build. The methodology map drives the encoding, the bottleneck analysis drives the feature scope, and the architecture document drives the stack. Nothing is re-discovered and nothing is re-billed.

If the recommendation is not yet, you keep every piece of it, along with a clear picture of what would have to change before a build makes sense.

We say not yet when the evidence says so. Saving you from a six-figure mistake is a good outcome for both of us.

Start with a Discovery

Tell us what you do and how people currently get it from you. We will come back with whether a Discovery makes sense and what it would cover.