The Build Log
Five entries. The same five, every time, on every engagement — you can read exactly how this runs before you commit to anything.
The Build Log
Survey
We read the system, the codebase, or the business process as it actually stands today — not as a set of assumptions. For a greenfield build, this means the constraints and the users; for a modernization job, it's the existing code and its failure points.
Ends with a written summary of what we found, sent to you — not held back for a sales call.
Specification
Scope, architecture, and price are written down and fixed before build starts. This is the document the fixed price on /pricing/ refers to.
The price you see is the price you pay for that scope — changes are logged and priced separately, not silently absorbed or silently billed.
Build
Development happens in weekly increments. Each week ends with a working demo of what shipped that week, not a status slide.
Weekly working software, not weekly meetings about software.
Verification
What was built is tested against the specification from entry 02 — functionally, and against the constraints found in entry 01 — before it's called done.
"Done" is checked against a written spec, not against a feeling.
Handover
Code, documentation, credentials and IP transfer on final payment. Support continues only if you choose a Maintenance tier — it's never required to get your own code.
You leave entry 05 owning everything, whether or not you ever engage us again.
WHAT WE COMMIT TO
- 01
You own the code and the IP on final payment.
Full transfer — source, documentation, credentials — no license fee, no lock-in.
- 02
You see working software every week.
A demo, not a status update, for the duration of any active build.
- 03
The price is fixed before we start.
Scope and cost are written into the specification; changes are logged and priced separately, never silently absorbed or billed.
- 04
Delivery is EU-based, data handled under GDPR.
Nothing about your project moves outside the terms we state in the Privacy Policy.
What makes this run on time
- A written brief, or a willingness to build one with us in the Survey step
- One decision-maker who can approve the specification and sign off on changes
- 20–30 minutes, once a week, for the working demo
- Access to whatever the project needs — an existing codebase, a test environment, a design system — as early as possible