Our method · AI-assisted, architect-approved
Read. Score. Gate. Sign.
The four steps behind every assessment, health check and sprint we deliver. AI does the first pass. An architect checks the work and signs the answer.
- The same four steps on every fixed-fee offer
- Scoring published
- Every readout signed
Four steps, every time
Each step has one job, and each one leaves a record you can check.
Read
Start from what you already have.
Contracts and amendments, invoices, ticket exports, provider reports and system data. AI does the first pass, pulling out terms, dates, counts and amounts. An architect checks each finding against its source, and anything that can’t be traced back to a document stays out of the readout.
You getFacts with their sources. Every finding opens to the contract term, invoice line, record or workshop behind it.
Score
Rank the options in the open.
You approve the criteria and weights before we score. Every score has a written reason, and where it helps, you can move the weights in the readout and watch what changes. AI use cases are scored on our published model.
You getA ranking you can check, and what would flip it.
Gate
Agree the pass mark before anyone spends.
Before a pilot, a program or a negotiation starts, we agree the numbers and dates that decide it: the pilot’s pass mark, the decision date, the fallback if something slips. Nobody moves the goalposts later.
You getA go or no-go you can call on the day, instead of arguing about it.
Sign
Put a name on the answer.
On client readouts, Lai Long, founder and principal architect, reviews and approves every finding. The readout carries that sign-off and its date, and it opens with the answer.
You getOne answer with a name behind it, as an interactive readout, a PDF record and a slide deck.
AI-assisted, architect-approved
AI makes the reading fast. People make every call.
What AI does
- Reads the documents you share and pulls out terms, dates, counts and amounts
- Drafts the calculations, the findings and a first version of the readout
- Checks totals and cross-references, so our time goes to judgment
What it never does
- Decides what we recommend
- Contacts your providers, or anyone else
- Approves, signs or sends anything
- Runs outside an environment you approve, or trains on your documents
Who approves. An architect checks every finding against its source. On client readouts, Lai Long reviews and approves every finding.
Your call. Prefer we didn’t use AI on some documents? Say so at kickoff. We’ll do that part by hand and agree any change to the timeline first.
How it runs in each fixed-fee offer
The same four steps, applied to the decision in front of you. Sign works the same way in all three.
| Offer | Read | Score | Gate |
|---|---|---|---|
| SAP ECC exit readiness assessment3 weeks · $19,500See a sample | SAP Readiness Check results, custom code usage, interfaces, forms, licenses and contracts | The S/4HANA paths, on criteria you weight in the first workshop, with what would flip the ranking | A decision date, the fallback if something slips, and the conditions that would change the answer |
| Provider contract and SLA health check2 weeks · $9,500See a sample | Up to three contracts, 90 days of tickets and service reports, and the invoices | Each provider against its own contract, with every finding tied to a contract term, invoice line or ticket | Claim windows and notice dates on one calendar, with a keep, renegotiate or rebid call ahead of each notice date |
| AI use-case sprint2 weeks · $12,500See a sample | How the work gets done today, from workshops with the people who do it, and the data each idea needs | 15 to 20 use cases on our published scoring model | The pilot’s pass marks and its go-or-no-go date, agreed before it starts |
Check it before you hire us
Advice is easier to trust when you can check it. The method, the scoring and the rules we work under are all public.
Put the method to work on your next decision.
A free 30-minute call with a solution architect. General inquiries: [email protected]