Endurance · Core Values
Three values, said plainly.
We don’t do poster values: no “heart,” no “resilience,” no “be a lion.” These are the three rules we actually run on, written the way we say them out loud.
01 · Core value
Always learning.
Humility and curiosity, every day.
We build inside other people's industries — freight desks, law firms, kitchens, capital markets — so learning fast isn't a virtue here, it's the job. Nobody has it all figured out, and trying to act smart shuts down the listening the work depends on.
Stay humble, ask more questions, and end every day a little less dumb than you started it. The systems we ship work the same way: every document, every correction, every operator conversation makes them smarter.
- In practice
- Ask more questions than you answer — a great second meeting is earned by the questions asked in the first.
- “I don't know yet” is a complete sentence — followed by going and finding out.
- Listen before you build — what the operator says shapes the system.
02 · Core value
Be of service.
Jump in. Make it happen.
Service here means motion: see the problem, take the problem — don't wait to be asked and don't route it through a layer. Inside the team, everyone has direct access to everyone; when you need someone, you get them.
Outside the team, everyone is busy — the question is whether our partners can tell they're a priority. They can, by how fast we move.
- In practice
- See it, own it — jump in without waiting to be asked.
- Direct access, no layers — when a teammate needs you, they get you.
- When a partner or client calls, they get a fast, real answer — busy is never the excuse.
03 · Core value
Finish the job.
Shipped isn't finished. Used is.
In our business the demo is the easy part — two exciting weeks, then the long middle: messy data, changed requirements, the third revision of the thing everyone thought was done. The job was never the code; it's a system the operator runs their morning on without us in the room.
We stay until it's that, and we finish it properly — numbers reconciled to zero, edge cases handled, root causes fixed instead of patched. We're named after a ship whose crew finished the expedition. Every man came home.
- In practice
- Launch is the midpoint — we stay until the system runs the client's day without us.
- The last 5% — edge cases, empty states, the awkward export — is the job, not extra credit.
- Reconcile to zero and fix the root cause — a patch that hides a problem is a debt, not a fix.