The Proof Is in the Artefacts
By Obaid Tariq, Founder & Lead Engineer · Last updated
“Partner” is cheap language. These three artefacts are the evidence: a decision log, a scope-change card, and a weekly report — the same three a client sees on a live engagement. No rival in the competitor analysis publishes all three together.
Illustrative sample — not a real client engagement — Sample SaaS MVP. No real client, no invented outcome.
(a) Decision log
Modelled on Rootstrap’s Ground Truth decision log, simplified to context, decision, owner, date, why, rejected alternatives. Every material decision gets its own entry, so knowledge does not leave when people do.
- Context
- Sample decision, shown to illustrate the format
- Decision
- Example decision (not a real one)
- Owner
- Founder & Lead Architect (sample)
- Date
- Sample date — not a real decision date
- Why
- Reason recorded alongside the decision
- Rejected alternatives
- Alternatives considered and set aside, with reasons
(b) Scope-change card
The Change Rule, as a card. Work does not start until the client signs it in the ticket — the full rule is on pricing.
Sample change card — Sample SaaS MVP
- What changes
- Example change (not a real request)
- Hours
- Shown on a live card; left blank in this sample
- Cost
- Shown on a live card; left blank in this sample
- Timeline impact
- Shown on a live card; left blank in this sample
- Your sign-off, recorded in the ticket
- Not signed — sample card, no work started
(c) Weekly report — sample week
The fixed weekly-report template, with a sample week. Cadence: Weekly planning (Mondays); development in 2-week sprints; Friday written progress updates; Working-software demonstrations at the end of each two-week sprint. The sample entries below are placeholders that show the format — they are not a claim that this work was delivered.
Sample week — Sample SaaS MVP
- Shipped this week
- Example: staging build of the agreed milestone scope (sample entry)
- Demo link
- Sample placeholder — no live link
- Tickets closed
- Sample tickets SAMPLE-101, SAMPLE-102 (sample entries)
- Blockers
- Example: none in this sample week
- Next week
- Example: next milestone scope, as agreed in Monday planning
- Burn vs budget
- Sample only — no figures shown, because no real budget exists for a sample project
The client view these reports sit in is previewed on client dashboard.
Work with a partner, not a vendor
Tell us what you want to build. You get a reply within 24 business hours, a 30-minute scoping call with the engineer who would lead it, and a written scope and quote.
Not ready to build? Explore Production Case Studies