How we work

Five phases. The scale changes. The method does not.

The same sequence runs on a single practice system and on a program spanning a dozen organizations. It exists because the expensive failures in custom software are all decided before any code is written: the wrong process modelled, a decision that cannot be reversed later, or a deliverable approved for the first time at the end.

How we work

The five phases.

1. Discovery

The operation as it actually runs, including the parts nobody documented, and what the current process costs.

2. Scope and architecture

A written scope, the integration surface, the decisions that cannot be reversed, and one price against it.

3. Demonstration

The system shown and approved before it is built, so the first thing you react to is not a finished invoice.

4. Build and verification

Delivery against the scope, each piece proven against the real process and the real data.

5. Deployment and support

Installed, documented, updating itself, and supported on terms written into the agreement.

Phases one and two

Discovery, then scope and architecture.

Phase 01. Discovery. We learn the work before we design anything, and we learn it from the people doing it rather than from an organization chart. The output is a written account of the process as it genuinely runs, which is almost never the process as it is described in a meeting. A product built on a description of a document is the single most common way this work goes wrong, and scope that covers only the first audience comes back as rework.

Phase 02. Scope and architecture. A written scope, and the decisions that are expensive to reverse taken deliberately and recorded with the reason. These are not technical preferences. They are commercial facts with a long tail. Decided here, because they cannot be retrofitted: how customer data is separated, who may do what, what is audited, how money is represented, what happens when something fails halfway, how data is exported and deleted, and how far a fault can spread.

The real artefact is read, not described

If the work produces a document, a workbook, a template or a paper form, we open the actual file and transcribe it.

The other humans are named

Not only your team: the client who receives the deliverable, the crew member on site, the lender reading the report.

What must not be replaced

The systems you keep are listed explicitly, with what each one owns.

The baseline

What the process costs now, in hours, agreed before the work starts so the result can be measured against something real.

Where the work runs

Cloud, private cloud or on premises, and what has to keep working with no connection.

One number against the scope

With payments tied to milestones rather than to elapsed time.

The integration surface

Named system by system, with the authoritative source for each record decided and written down.

Phases three and four

Demonstration, then build and verification.

Phase 03. Demonstration. Before the build, you are shown the system: every screen, every button, every setting and the real words on them, in the real design. You approve it or you send it back, and sending it back costs a conversation rather than a change order. This is the cheapest possible place to change your mind, and it is the phase most suppliers skip.

Phase 04. Build and verification. Delivery against the approved scope, in chunks, each one proven before the next begins. Verification here means something specific and it is worth being plain about what. Finding a handler in the source is not evidence that a person can use it.

Every control the finished thing will have

Present, in its real place, with the real labels.

Where it replaces a document

The real document is shown beside it, with its own headings in its own order.

A rejection returns to scope

Never forward into the build.

Each piece proven against real data

And the real written procedure, not against a convenient sample.

Every check is made to fail on purpose first

The failure is planted, watched and recorded before the check is trusted.

A real tap and a real mouse click

Interfaces proven at phone width and at desktop width, in a real browser.

An integration is not counted as built

Until it has read one real record out of your live system.

One complete job of yours

Driven through the finished product, producing the real deliverable, before anything is called done.

Phase five, and the limits

Deployment and support.

Phase 05. Deployment and support. Installed where the work happens, documented for someone who was not in any of the earlier conversations, and able to receive a fix. A fix nobody can receive is not a fix.

An update path from the first release

Signed, checked before anything runs, and never installed behind anyone's back.

A sign-in never changes on an update

Someone who can get in today gets in the same way tomorrow.

Documentation that stands alone

Plain language, a route inventory and the decision record, kept with the code.

Support on written terms

With a named lead who was there from discovery.

What we do not do.

Stated plainly, because knowing where a supplier stops is worth more than a list of everything they claim.

An hourly engagement pays a supplier for being slow, and it hands you all of the risk of an open-ended estimate. Your data and, where that is the agreement, your source stay yours, so leaving is a documented handover rather than a negotiation. A rip and replace proposal is usually a supplier's convenience, so we integrate what works and replace only what is costing money. A number given before the work is understood is a number that changes later, which is the same thing as not having quoted. Automations ship switched off, and anything that produces a figure, a grading or an outbound message presents it for approval. What we hold, you can verify.

We do not bill by the hour

One number against a written scope.

We do not hold your hosting

Your data and, where that is the agreement, your source.

We do not replace systems that work

We integrate what works and replace only what is costing money.

We do not let software act unsupervised

Anything that produces a figure, a grading or an outbound message presents it for approval.

We do not quote before discovery

A number given before the work is understood is a number that changes later.

We do not overstate our credentials

We complete your security questionnaire and work through your vendor review.

Discovery is a conversation. Start with the one you are already having.

Programs nationwide, United States. To start: call (252) 666-7217 or email [email protected].