Skip to content

Capabilities

Strategy and systems design: decide before the code hardens

Every software project answers the same questions: how the work really runs, what should change, which parts need automation or AI, what the system's parts are, who owns each record, what to build and what to keep, and in what order. Answered on paper, each one is a conversation and a written decision. Found out halfway through the build, it's a rewrite. We answer them first, as many as the job needs, and write the answers down.
Talk through your projectSee all ten capabilities ↓
Discovery and architecture · the home-services businessUnderstandHow does close-out really run?How does close-out really run?business process discovery11 steps, not 6 · 44 min of work over 2 days 18 hWhat's connected, and where does it break?What's connected, and where does it break?current state mapping12 people and tools · 4 failure pointsDecide what changesWhat should close-out become?What should close-out become?future-state design5 states and 3 exceptions, each with an ownerWhich steps are worth automating?Which steps are worth automating?automation opportunity analysis3 first · 1 with a check · 3 stay as they areWhere would AI help?Where would AI help?ai opportunity analysis3 places · 2 with a person decidingDesign the systemWhat are the parts?What are the parts?solution architecture7 parts for 5 requirements · 1 left outWho owns each record?Who owns each record?integration architecture6 kinds of record, one owner eachWhere is each question answered?Where is each question answered?data architecturetotals from an hourly copy, not the live systemBuild, buy or keep?Build, buy or keep?technology selectionkeep the accounting software, connect to itSequenceIn what order?In what order?technical roadmappingone check first, then 4 stages, each usableThe owner decides: go ahead with the first check and stage 1

Ten capabilities, in the order they're used

Each answers one question. Later answers lean on earlier ones, so the cheap questions come first.

  1. 01

    Understand

    How does it work today?

  2. 02

    Decide what changes

    What should it become?

  3. 03

    Design the system

    What will carry it?

  4. 04

    Sequence

    In what order?

What you have at the end

Documents you can act on, whoever builds the system. Each one answers a question someone will otherwise ask halfway through the build.
Current-state mapwhere does work break today?you, to agree what's worth fixing
Future-state designwhat happens to every case, and who owns it?whoever builds the workflow
Opportunity listwhat to automate, where AI helps, what to leave aloneyou, to choose the first stage
Architecture and ownershipwhat are the parts, and which system owns each record?the developers
Decision recordswhat was chosen, what was given up, what would change itanyone revisiting a choice later
Roadmapwhat comes first, and what's usable after each stage?you, at every review

As much as the job needs

Not every project needs all ten. A small connection between two tools needs a few questions answered, not a phase of consulting.

Send finished jobs to accounting

  1. Business Process Discovery

    skip

  2. Current State Mapping

    just the two tools and the people between them

    needed

  3. Future-State Design

    skip

  4. Automation Opportunity Analysis

    skip

  5. AI Opportunity Analysis

    skip

  6. Solution Architecture

    skip

  7. Integration Architecture

    who owns the invoice

    needed

  8. Data Architecture

    skip

  9. Technology Selection

    connect directly, or through a workflow tool

    needed

  10. Technical Roadmapping

    skip

Three questions, answered before the connection is built.

Straight to building, or decided first

Straight to building

  1. 01The first tool that seems to fit
  2. 02Automating the procedure as written
  3. 03Records copied wherever they're needed
  4. 04Everything in one big release
  5. 05Decisions remembered by whoever made them

The questions still get answered, in the middle of the build, by whoever is there.

Decided first

  1. 01Tools chosen against your requirements
  2. 02Automating the work as it really runs
  3. 03One owner for each kind of record
  4. 04Stages that are each useful on their own
  5. 05Decisions written down with their reasons

Building starts with fewer surprises, and the expensive choices were made deliberately.

Start with how sure you are

  1. Business Process Discovery

    “We know it's slow, not why”

    Map how the work really runs before choosing anything to build.

    See how it works →

  2. Automation Opportunity Analysis

    “We want to automate, but what first?”

    Rank the candidates by time saved and risk, then start with one.

    See how it works →

  3. Solution Architecture

    “We know what to build, not how it fits”

    Decide which system owns what before code makes the choice for you.

    See how it works →

Related pages

Where they come together

Related