Pillars & Principles

What stays constant across five industries

Gonav works in workspaces, software, payments, mobility and travel AI. These are the beliefs we share between them, and the rules we operate by.

Pillars

Five beliefs we build on

01

Stay close to the work

Our teams sit inside the operation they are improving.

People work from the warehouse floor, the finance close, the front desk. Distance from the problem is expensive, so we design it out.

02

Prove it small

Test on real users and real money before scaling anything.

A result has to hold up on live customers and a real month-end before it gets a growth budget. We are patient with proof and quick after it.

03

Build once, reuse often

Every project leaves tools the next one can pick up.

Payments plumbing, routing engines, the workplace stack — each practice hands its best components to the next. The company gets faster as it builds.

04

Own the outcome

We are measured by the result, not the hours.

Every engagement has a named lead and one number to move, reviewed every quarter. Output is not the same as outcome.

05

Protect trust

Client, user and money are handled with care first.

Trust is slow to build and quick to spend, and it is not on any balance sheet. We make decisions as if it were.

Principles

Seven rules for everyday work

Short enough to remember in a meeting. Specific enough to settle a disagreement.

  1. 01

    Decide the goal before the plan.

    Agree what “done” looks like first.

  2. 02

    Ship the smallest useful version first.

    Get a real signal, not a demo.

  3. 03

    Write decisions down where everyone can see them.

    If it changed the plan, it is documented.

  4. 04

    Build so someone else can run it.

    Assume a handover next quarter.

  5. 05

    Measure what users feel.

    Instrument the outcome, not the release.

  6. 06

    Use proven tools for important work.

    Save the novelty budget for what is genuinely new.

  7. 07

    Leave things clearer than you found them.

    Better docs and defaults at the end than the start.

In practice

Where the rules show up

In hiring

We look for people who have run something and are comfortable being wrong early. Titles matter less than that.

In review

Every project review asks two questions: what did the evidence say, and what did we leave clearer than we found it?

In saying no

If work needs us to spend trust we cannot rebuild, or scale before the data is in, it is a no — whatever the revenue.

More about the company