How we work
The same method on every project, written down after twenty-five years of programmes where errors were costly.
- 1
Access and NDA first
No data is read before an NDA is signed and access is agreed.
- 2
Two-week discovery
A security check, a map of your data and processes, and a first page for the owner built on your own data.
- 3
One plan of record
A numbered list of what we build, in order, each with how you will know it works. New requests go on the plan before anything starts.
- 4
Short build cycles
AI tools and developers build against the plan in one- to two-week cycles. You see working screens each cycle.
- 5
Your yes before anything goes live
Each release needs the owner's yes in words, with a backup before every data change.
- 6
Independent checks
Separate reviewers check every figure against the source. A green build is not proof; the live page is.
- 7
Plain reports
Every report has four parts: done, skipped or failed, needs you, next. A one-page built-versus-backlog view is kept current.
Quality rules
Each rule was written after something went wrong once. They apply to our own work and to every AI tool we use.
- A green build is not proof. We open the live page and check it.
- Every calculation gets a test with an answer known in advance.
- What is established and what is suspected are worded differently.
- The machine proposes; a person in your company signs.
- Each fact has one source.
- We say what is still unfinished.
AI, used carefully
AI drafts, checks and reads documents. It does not send messages, approve payments or change your ERP on its own.
Unattended AI routines only record what they find, with a monthly spending cap shown on the control room.
Staff question desks answer from a fixed set of questions with each person's own access, so they cannot invent figures or see more than that person may.
We use the same rule on this website: an agent drafts a reply to every enquiry, and a person reads and approves it before anything is sent.
How we charge
We charge for know-how, quoted per task. The software, the code and the systems we build are included and belong to you.
More on how we chargeOur fees cover the analysis, advice and project management our team puts into your problem. Writing software now costs very little, so we do not bill for code by the line or charge licence fees.
The systems we build are included in the fee and handed over with the source code and the right to change them. You can keep them, extend them or pass them to another supplier.
Every task is quoted before it starts, after a first conversation.
More sales, fewer systems, run by your team
Every engagement has an end date. We measure it by what your own staff can run after we leave, and by what the business costs to operate afterwards.
More sales
The record shows which customers, products and channels produce the revenue, often for the first time. Sales decisions are then based on that record.
Your management takes it over
The system belongs to your team. It uses their own terms and runs on the phones they already carry. The chief executive reads the figures directly, without going through us or anyone else.
The legacy bill goes
Most businesses pay every month for tools nobody opens, or for several products doing the same job. We find them as part of the work. Switching them off is usually the quickest saving.
Workflows built around the work
Workflows are rebuilt around what the business does today. Old software limits that staff have worked around for years are removed.
A base for what you build next
One shared record of the business, with room to grow. Anything you build afterwards costs less because it starts from that record, and the company can take on projects it could not attempt before.
When we leave, the chief executive has direct control of the systems and the figures.
Book a first conversation
Thirty minutes, by video. Tell us what takes too long today or what you cannot see. You get a confirmation by email from ppcn.xyz.