ไทย
Menu

How we work · Sample documents

See the work before you buy it.

Five documents you receive on a Keel North project, shown from one fictional project. The format is the real one. The client, names and numbers are made up.

  1. 01Weekly written updateEvery week of a build
  2. 02Risk registerIn the Blueprint, then kept up to date
  3. 03Fixed quoteAt the end of the Blueprint
  4. 04Handover packAt launch
  5. 05Takeover audit reportFor a system someone else built

Sheet 01 · Every week of a build

Weekly written update

You always know what was done, what is next, what is blocked, and what could move a date. Nobody has to chase anyone.

Week
6 of 10
Milestone
2 of 3
Next demo
31 Oct, unchanged

On track

Done this week

  • Leave requests with two-step approval are on the test link.
  • Managers can approve from LINE on Android and iOS.
  • 412 staff records imported from the HR spreadsheet. 9 have no manager set: the list is attached for HR.

Try it

  1. Open the test link and sign in as manager.demo.
  2. Approve the leave request from staff.demo.
  3. The staff member's balance drops by the days taken, and the approval appears in the audit log.

Next week

  • Overtime requests.
  • The monthly export for payroll, in the file format HR agreed in week 1.

Blocked

  • Microsoft sign-in needs an app registration from IT, requested on 14 Oct. Until then the test link uses a temporary login.

Risks

  • If the registration arrives after 28 Oct, the milestone 2 demo may move by up to three days. We will confirm by 28 Oct.

Written by the engineer building it. Reply to this email with questions; there is no meeting to book.

Sheet 02 · In the Blueprint, then kept up to date

Risk register

Every risk has an owner and a response before the build starts, so none of them arrives as a surprise.

IDRiskLikelihoodImpactOwnerResponse
R1The payroll export format changes during the buildMediumHighHR leadA sample file is agreed in week 1. Changes after that are priced before they are built.
R2Microsoft sign-in waits on IT approvalHighMediumITRequested in the first Blueprint week. A temporary login keeps the build moving.
R3Staff records have gaps, such as missing managersHighMediumHRThe import report lists every gap. HR fixes them in the spreadsheet before launch.
R4Leave records are personal data under PDPACertainHighKeel NorthAccess by role, an audit log of every change, and a signed data processing agreement.
R5Managers keep approving by chat insteadMediumHighHR leadApprovals happen in LINE, which managers already use. Two managers try the prototype in the Blueprint.

Excerpt: five of the register's fourteen risks.

Sheet 03 · At the end of the Blueprint

Fixed quote

One price for a written scope, what isn't included, the dates, and how changes are handled. No hourly billing.

01Scope
Every feature in plain words, with what it does and who uses it.
02Not included
Written down, so nobody discovers it at the end.
03Price
One fixed price in baht. No hourly billing and no day rates.
04Payments
40 / 40 / 20 at three milestones, each signed off at a live demo before you pay it.
05Dates
A date for each milestone, and what we need from you by when.
06Changes
Priced and agreed before they are built, never billed afterwards.
07Warranty
12 months of bug fixes on everything in the scope.

Excerpt · Milestones

Milestone 1 · Leave requests, approvals in LINE, staff import40%
Milestone 2 · Overtime, payroll export, Microsoft sign-in40%
Milestone 3 · Reports, handover pack, launch20%
Each milestone is paid after its live demo is signed off.100%

Sheet 04 · At launch

Handover pack

Your team, or any other vendor, can run and change the system without us.

Contents

  1. 1System mapComponents, data flows and integrations on one page, with who holds which account.
  2. 2Access registerEvery account and repository, in your organisation's name, with two owners on your side.
  3. 3Run bookHow to deploy, roll back, restore a backup and change a password or key, step by step.
  4. 4Source code and testsIn your repository from day one, with the automated tests and how to run them.
  5. 5GuidesFor administrators and for users, in Thai and English.
  6. 6Security notesThe controls in place, the personal data held and where, for your PDPA records.
  7. 7Known limitsOpen issues and anything deliberately left out, so nothing is a surprise later.
  8. 8WarrantyThe 12-month terms and how to report a bug.

Sheet 05 · For a system someone else built

Takeover audit report

What you actually own, what is at risk, and a fixed price to make it safe, in one to two weeks.

Contents

  1. 1InventoryThe code, servers, accounts, licences and monthly costs, in one list.
  2. 2Access moved to youEach repository and admin account moved into your name, with the date it moved.
  3. 3Code healthStructure, tests, and libraries with known security problems.
  4. 4Security and PDPA reviewHow personal data is stored, who can reach it, and what is logged.
  5. 5Risk listRanked by impact, each with the fix and its size.
  6. 6Fixed quoteThe price to stabilise it, and what support would cost after.

Questions about any of these?

Ask on a 30-minute call, at no charge. We will walk you through how each document is made and what it would hold for your project.

Book a 30-minute call →