// how we work

Depth over breadth. The floor is the source.

Five commitments that shape every engagement. We mean each one — they're testable.

01

Depth over breadth.

We sooner turn a client down than stretch too thin. Our roster is capped at five active builds. A client we onboard is one we intend to keep for years.

Test: ask a current client how to reach Joseph. The answer should be a phone number, not a ticket queue.

02

The floor is the source.

The best specifications come from the people doing the work, not from org charts. We interview dispatchers, machinists, bookkeepers, receivers — and we quote their own words in the system.

Test: search the codebase of any LogsOfN system for client-team vocabulary. We don't normalise away local language.

03

Software is infrastructure.

Not a project. Not a deliverable. Not a website. We build for the decade, not the launch. Backups, audit trails, RLS, monitoring, role permissions — non-negotiable from day one.

Test: every entity has an audit log row from the first migration. No exceptions.

04

Authors stay maintainers.

The engineer who writes the code is the engineer who answers the phone five years on. We don't subcontract; we don't offshore; we don't roll off after launch.

Test: there is no tier-three support team because every issue is tier-one with us.

05

Plain numbers.

Per-seat pricing, monthly invoicing, no JV games. The fee structure on day one is the fee structure five years in, adjusted only for CPI.

Test: the SOW is short, the renewal is automatic, and the invoice fits on one page.

// the shape of an engagement

Twelve weeks to live.

Workshop, map, build, live and stay — the four steps in full, with the weeks each one takes.

  1. 01

    Workshop

    1. W0
      WorkshopHalf-day on the floor with the team. We listen, map vocabulary, write the brief in the client's language.
  2. 02

    Map

    1. W1–2
      FoundationsTokens, schema, auth, deploy. Brand applied. Audit log on from row one.
  3. 03

    Build

    1. W3–5
      Core baysClients, finance, people. The bays the office runs on.
    2. W6–8
      Operational baysFleet, workshop, deliveries. The bays the floor runs on.
    3. W9–10
      MobileiOS + Android. Drivers, ops, director flows. Offline-first.
  4. 04

    Live + stay

    1. W11
      MigrationLive data import, parallel run, sign-off.
    2. W12
      CutoverGo-live. We stay on for the first 30 days — the authors on the phone, not a support tier.
// the promise

Tell us how you want to run your company. We'll build the system together — and stay with you as it grows.

Begin the brief