How a project runs.

Four steps, fixed price agreed before anything starts.

The steps

  1. Map the process. You describe what is typed twice and where things get lost. I send back the fields, folders and the finished document, plus a fixed price. No build starts without this on paper.
  2. Build. I set it up on a copy first: templates, numbering, folder structure, access codes.
  3. You test. The tool is installed in your own Google account with test data. You break it, I fix it.
  4. Handover. Setup guide in plain language, source code, and 14 days of fixes included.

What I need from you

A sample document

The file you keep retyping, in Word, Docs or PDF.

A Drive folder

Owned by your company account, where the system files everything.

Your list data

Prices, units, staff, positions. A rough spreadsheet is enough.

Who uses it

Which staff, and what they must not be able to change.

Timeline

DayWhat happensYour side
0Scope and fixed quoteAnswer five questions
1 to 2Template and data structureSend the sample document
3 to 5Build and internal testCreate the Drive folder
6You test with real dataTry to break it
7Handover and guideRun it with your team

Delays almost always come from account access, not from code.

Try the demos