Process

How a project runs.

Four steps, a fixed price agreed before anything starts. Most builds take three to fourteen days from the day access and the brief are in.

01 The steps

Nothing is built before it is on paper.

/01

Map the process

You describe what is typed twice and where things get lost. Arkhitem sends back the fields, folders and the finished document, plus a fixed price. No build starts without this on paper.

/02

Build

Arkhitem sets it up on a copy first: templates, numbering, folder structure, access codes.

/03

You test

The tool is installed in your own Google account with test data. You break it, we fix it.

/04

Handover

Setup guide in plain language, source code, and 14 days of fixes included.

02 Your side

What Arkhitem needs from you.

/01

A sample document

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

/02

A Drive folder

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

/03

Your list data

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

/04

Who uses it

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

03 Timeline

A seven day System build.

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

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

Talk it through first

Your business deserves better systems.

A free 30 minute call. You describe what your team types twice, we tell you whether it is worth automating and roughly what it would cost. No deck, no obligation.

Free consult