Start from requirements or from legacy source. Requirements, design, build, four levels of testing, migration, and operations — every document a large Japanese engagement must deliver, produced as stage output — not one missing. Deploy in one click. Progress shows per job (one run for one issue), as in this figure.
From requirements, or from legacy.
Just hand over the requirement documents, interview notes and business materials. The AI turns them into a requirements specification, and the same job carries the work through design, build, testing, migration and operations.
We read the actual COBOL, Java, VB or PL/SQL source and recover the current specification. Even a thirty-year-old asset whose design documents are long gone can start from the next step.
↓ Both merge into the same seven phases ↓
The job advances. The documents land. The system runs.
Each phase is closed by a check stamp — a person stamps it, the AI writes it. A rejection returns to the previous phase with a reason and the AI does it again. Phase 05 Testing has four stages: unit, integration, system and acceptance.
Not one missing.
Not only the final documents. The intermediate ones too — test plans and reports for every level, review records, migration rehearsal records, weekly progress reports — all assembled to the delivery standard of a large Japanese engagement. Anything marked "Automatic" does not even have to be written: it comes out of the job's record.
The standard template (標準納品規程 v3) covers 100 documents in total. See the deliverables catalogue on the product page for the breakdown. We can also swap in your own delivery standard. See the catalogue ▸
Start by looking at a real job.
Backwards, forwards, or both at once.
We reverse-read 410,000 lines of COBOL, restored the current specification, then renewed the system. Acceptance testing passed in the customer’s own sign-off format.
Forward generation. Every document from requirements through acceptance was delivered to standard, and the audit department passed the document review in one round.
Renewal (Entry B) and new build (Entry A) jobs ran in parallel in one project, with the shared platform work referenced across both.
These case studies are anonymised, PoC-stage results. Company names, logos and confirmed figures will replace this block once the client's permission is granted. We never publish a logo without consent.
Priced per engagement.
Composed according to the scale of your assets, your delivery standard and your team. Starting with a PoC — one module, four weeks — is the standard contract.
Makit is not project-management software.
There is no screen for entering progress and no feature for writing reports — the AI performs the phases, and people only apply the check stamp.
See how each stage is progressing and which deliverables are waiting for your approval.