Build
Workflow Build
One named piece of work in your office, designed with the people who do it today, built, tested against your own examples, handed over with a plain language description you keep. It ends. It is not a subscription.
01In detail
- What it is
- Find the job, write it down and get it approved, build and check against test cases drawn from their real work, hand over with a configuration record and a data siting note. The test cases are the acceptance standard and nothing else is.
- Why now
- An engagement competes with a hire or a consultant, not with a thirty dollar app. Those are different decisions.
- What you end up with
- You end up owning something, and a written account of why it behaves the way it does.
- What it never does
Start before the design note is approved in writing.
Hand over without the four documents: how it works, what it is configured to do and to refuse, where the data sits, and one training session.
- Where it stands
- Offered now; no client build has been handed over yet.
02Get an audit