$ cat values.md

The Principles We
Build Everything On

Values aren't a wall poster. They're the decisions we make when nobody's watching.

6
core principles · established 2005 · unchanged since

What We Stand For

Six principles that have guided every client engagement, every hiring decision, and every architecture choice for 21 years.

[01]

Fixed price is a promise, not a product

We commit to scope and price before a single line of code is written. If we underestimate, that's our problem. The client never pays for our mistakes.

// immovable
[02]

Senior engineers, always

We don't staff projects with juniors and hope for the best. Every engagement is led by engineers with 10+ years in regulated industries. You're paying for expertise, not headcount.

// no exceptions
[03]

Compliance is designed in, not bolted on

We treat regulatory requirements as architecture constraints, not afterthoughts. GDPR, HIPAA, Solvency II — these shape our technical decisions from day one.

// first-class constraint
[04]

Honest over comfortable

We tell you when something won't work. We push back on bad ideas even when you're the client. We'd rather lose a deal than deliver something we don't believe in.

// always
[05]

Quality has no expiry date

We write code we're not embarrassed by. We test thoroughly. We document properly. Because the engineer who inherits this in five years deserves that.

// non-negotiable
[06]

Long relationships over quick wins

DEKRA: 10+ years. World Vision: 9+ years. We measure success in decades, not delivery dates. The best work happens when both sides are in it for the long term.

// 21 years of proof
$ tail -n 1 lessons-learned.log
"
We've never had a project fail due to technical reasons. Every project that's struggled has struggled because of communication, unclear requirements, or rushed decisions. We've built our entire process to prevent that.
Yameo Engineering Team 21 years · 200+ projects
0 projects failed for technical reasons
0 failed regulatory audits
0 budget overruns with DEKRA (10y)

What These Values Look Like in Practice

Values without behaviour are fiction. Here's how ours show up in the work.

We price before we start

Every engagement begins with a scoping phase that produces a fixed-price contract. No estimate ranges. No "it depends." One number, signed before build begins.

We decline projects we can't do well

If a project is outside our regulated-industry expertise, we say no. We refer elsewhere. We'd rather lose the revenue than deliver average work.

We push back in scoping, not production

When a client asks for something technically flawed or compliance-risky, we say so in discovery — not six months in when reverting costs a fortune.

We write documentation the next team can use

Every project ships with architecture documentation, API specifications, and runbooks. Not because clients ask for it — because it's the right thing to do.

We measure client success, not project delivery

We ask about business outcomes months after delivery, not just whether we hit the timeline. DEKRA and World Vision have been clients for over a decade because we do.

We absorb our estimation mistakes

If we scope a project incorrectly and run over budget, that is our commercial risk — not the client's. This has happened. We absorbed the cost. That's what fixed price means.

$ ./work-with-us.sh --values-aligned

Work With a Team That Means It

If these values sound like how you want your project run, let's talk. Tell us what you're building and we'll come back with a fixed-price proposal and a clear view of how we'd approach your compliance requirements.

Start the Conversation