Gate: Contact
Route maps

Three routes

Every project follows one of these shapes. Stops are where you see something real and decide whether to continue. Interchange squares mark where routes can switch.

New build

LINE GC NEW

From an idea to software people use. Straight line, because the destination is clear and nothing has to be untangled first.

  1. DiscoveryWho it is for, what success looks like, what is out of scope
  2. PrototypeClickable screens to test the idea before code is written
  3. PlanAgreed first release and rough order of work
  4. BuildShort cycles with working software to review each time
  5. First releaseLive with real users, issues logged and prioritised

Rescue

LINE GC RES

For software that is late, unstable or abandoned by a previous supplier. This route doubles back on purpose: we look before we touch.

  1. AccessCode, hosting, accounts and documents gathered in one place
  2. Code reviewWritten findings: what is sound, what is risky
  3. DecisionRepair, partially rebuild or replace, with reasons
  4. StabiliseFix the issues that hurt users first
  5. Stable againThen join the Extension line if more is needed

Extension

LINE GC EXT

Your software works; it needs new features, integrations or capacity. A circular line, because extension tends to repeat.

  1. OrientationWe learn your codebase and conventions
  2. RequestOne feature or integration described clearly
  3. Build & testAdded alongside existing behaviour, not over it
  4. ReleaseShipped with notes on what changed
  5. Back to RequestLoop again, or move to ongoing support

Not sure which line you are on? Try the three-question selector or ask at the gate.