Business Process · Operating Manual

Deal to delivery, then the retainer.

10

stages, deal closed to retainer

2

gates the process cannot pass

5wk

signature to acceptance, read‑only scope

1yr

support retainer, renewing

The Flow

Ten stages. Two gates.

Phase 1 · Sell
01

Deal closed

Partner closes. Our operation starts.

→ signed engagement

02

Workflow engineering

Map their process, systems, data, KPIs. Collect sample exports.

→ workflow map + sample data

2–3 days
03

Designing the spec

Dashboards, automations, data sources, acceptance criteria.

→ Spec.md

2 days
Gate Client signs the spec · setup fee invoiced
Phase 2 · Excite
04

Demo shared

Their logo, their KPIs, mocked numbers. Live in days. Excites the boss, validates the spec early.

→ client.wateera.net

1 day
Phase 3 · Build
05

Copying Wateera template

Template copied, packages installed, theme set, roadmap generated from the spec.

→ client-{name} repo

1 day
06

Build sessions

One task, one session. Tests + docs + commit + push.

↻ until roadmap complete

~3 weeks
07

Quality gate

End‑to‑end test, every spec line self‑checked, using Codex and CodeRabbit for review.

→ internal pass sheet

2 days
Phase 4 · Deliver
08

Acceptance walkthrough

The client accepts the work.

→ written acceptance

Open
Gate Delivery
Phase 4 · Deliver · continued
09

Go‑live + final tour

Installed on their servers. Handover pack delivered.

→ system + pack

open · their testing
Phase 5 · Support
10

Retainer

Keep it running.

1 year, renewing
New feature → mini‑spec → stages 03–09 again, smaller
Timeline

Five weeks

After signing the deal.

Week 1

Workflow engineering · spec · signature

Week 2

Demo · bootstrap · build starts

Week 3

Build sessions

Week 4

Build sessions

Week 5

Quality gate · acceptance

Repo Architecture

One template.

wateera-template copied once · then theirs use this template client-sunbulah own repo · own roadmap client-b own repo · own roadmap client-c … 100 own repo · own roadmap imported · updated by version bump wateera-packages tokens · ui · auth · core · connectors · tour-kit
Copied

template

Imported

packages

Per client

theme file

What Lives Where

Theirs to keep, ours to run.

wateera-template copied · becomes theirs
  • Docs set — scope, roadmap, decisions, architecture, support
  • Quality machine — hooks, CI, lint, tests, golden datasets
  • Tour folder
  • App skeleton that imports the packages
wateera-packages imported · stays ours
  • tokens + ui — the Wateera look and the shell
  • auth — login, users, roles
  • core — config, audit log, errors, health
  • connectors — SAP · Oracle · Odoo adapters
  • tour-kit — showcase components
Handover Pack

What the client gets away with.

The system

Installed and running on their servers.

Tour link

Shareable showcase. Sells for us.

User guide

Short, screenshots, per role.

Training session

Recorded.

Support terms

Covered, response, what costs extra.

Acceptance record

Defines “working” contractually.