How we lead, decide, and build at Kruiz. This is the shared language for every leader here — founders today, and the executives we bring in next. Read it to learn the system; return to it to teach it. Two disciplines run the whole company: a rhythm for how we operate, and a sequence for how we decide what to build.
Operating rhythm adapted from Ryan Blair's P.R.O.C.E.S.S. (AlterCall). Build sequence adapted from Musk's five-step method. Translated into Kruiz practice.
Seven stages, run in order. The order is the teaching: you don't communicate before you've restricted, and you don't scale skills before you've committed. For each stage — the principle, why it matters, how it looks here, and the standard a Kruiz leader is held to.
| Stage | The discipline | Held to this standard |
|---|---|---|
| PPrayer | Go to the Source first, then release the outcome | Seek guidance, clarity, and direction from the Source before you act; then own the input and release the result. |
| RRestriction | Restrict the reactive — small light for the greater Light | Name the reactive "yes" you're restricting, the pattern it corrects, and the greater "yes" it protects. |
| OOath | Commit only what you'll honor | You put an owner and a date on everything and flag a slip early — full ownership is honesty about a miss, not never missing. |
| CCommunication | Connect before you direct | You write decisions where the team can find them, and your feedback is specific and kind. |
| EExcellence | It sells itself | You get the work right before it ships, and let proof and testimonials — not adjectives — make the case for it. |
| SSkills | Build what scales, hire what multiplies | You can name the one bottleneck most slowing the company down, and you're actively removing it. |
| SService | Sales follows service, service follows purpose | For anything you build, you can say in the customer's own words which rung it moves: make money, save time, reduce risk, or elevate status. |
Leaders make their worst calls when they're gripping an outcome — anxious about how it will turn out and trying to force it. The discipline is the opposite: get quiet, decide from clarity rather than fear, and act without needing to control the result. Whatever a leader's beliefs, the behavior is the same — do your part fully, then let reality tell you what happened. Don't decide the ending in advance. When you're waiting on an answer you don't yet know, the temptation is to convince yourself it's already a "no" and act hurt or defeated. Wait for the actual evidence before you write the story.
The APHIS partnership push started upstream — going to the source of the compliance problem instead of grinding on it — then the outcome was released. Three emails out, and we treat the wait as neutral: a reply is information, silence is information, a "no" is information. None of it is a verdict on the company.
You go to the Source for clarity before you act, move on the direction you receive, and release the result.
Re-deciding the same thing hourly; treating a delay as proof it won't work.
The reactive "yes" — building because someone asked, chasing whatever's shiny — is exactly the pattern to correct. A startup dies of too many yeses, not too few. Every parked feature is capacity returned to the thing that's actually paying. Restriction is not neglect — it's a documented, defended choice with a reason attached.
Take front-desk lookup — a reasonable feature a clinic could ask for. Say "yes" to it now and you're polishing a screen with no reliable data underneath it; the bigger "yes" that costs is the ETL pipeline every live clinic depends on. So we parked it behind ETL. The same trade runs through every "no":
Every "no" protects the same "yes": the clinics already live on the platform.
You can name the reactive "yes" you're restricting, the pattern it corrects, and the greater "yes" it protects.
Mistaking noise for signal — building because a customer asked once, with no gate and no reason logged. As Jobs put it, focus is saying "no" to a thousand good ideas so the few great ones actually get built.
A team runs on the reliability of its commitments, not the ambition of them. An owner and a date turn intention into an oath. We'd rather hear "I need another day" up front than discover a silent miss at the deadline.
The ship list is a wall of oaths, each with a name and a due date — shipping-cost visibility, wet-ink instructions, Belize support ahead of the client's travel date, the security layer. The posture is to own your input completely — honestly, and as optimistically as you honestly can — then release the result.
Everything has an owner and a date, and the moment something might slip you say so — early. That's full ownership: not a promise you'll never miss, but the honesty to raise it. Everyone's human and some things are outside your control — there's no punishment for a mistake. We learn from it, get ahead of it, and move on.
Vague ownership ("we'll figure it out"); the silent miss — a deadline that quietly moves with no conversation. The failure isn't the slip, it's not naming it.
Most execution failures are communication failures wearing a costume. Clear ownership, decisions written down, and feedback that lands without defensiveness are what let a small team move fast without breaking trust.
The notification design was decided by outcome, not habit — approvals reach pet owners, rejections stay with the vet so owners don't panic. Standups surface bugs without blame: "is this intended?" over "this is broken." Roles get written into the PRD so the same question isn't relitigated.
Decisions are written where the team can find them; feedback is specific and kind.
Firing off something charged over Google Chat or text instead of talking it through live, where tone gets read wrong. Shutting a teammate down with "you already said that" instead of asking why it still matters to them. Winning the argument but losing the room — being right in a way that leaves people less willing to speak up next time.
Credibility is earned before the ask, not during it. Excellence is the cheapest marketing we have: a customer who says the product is better than the alternatives is worth more than any pitch we could write or ad we could run.
The technical evidence pack for APHIS — reproducible edge cases, real logs, measured volume — is built before the partnership is pitched, so we arrive credible. And the proof shows up unprompted: an onboarded clinic called Kruiz more useful than the competitors and said they'd advertise it. That's excellence doing the selling.
The work is right before it ships, and we let proof and testimonials — not adjectives — make the case for it. That's why word of mouth is our most powerful channel.
Selling ahead of the build; shipping rough and planning to "do it over" later. And as we mature, the opposite trap — mistaking excellence for perfectionism: "right" means it works and holds up in real use, not polished past the point of shipping.
You're judged by the capacity you build, not the hours you log — the systems and people that keep working when you're not in the room. Three habits get you there: put your effort where it pays (the 70-20-10 split below), hire people who make everyone around them better (multipliers, not just more hands), and stay honest about the one bottleneck slowing everything else down.
Roughly 70% on the proven core — the full health-cert automation vets actually onboard for — 20% on what deepens and widens it, and 10% on bets we're willing to lose. It keeps most of the team on what already works while still leaving room to explore.
It's funding — and it comes wrapped in a chicken-and-egg. To get our investor re-engaged, we need to show traction: vets onboarded, MRR and ARR climbing, and a growing count of successful health certs. But traction is exactly what more funding would let us build faster. The way through is the input we actually control — prove the traction. This is Prayer and Oath together: go to the Source first for guidance, own the work fully and honestly, and release the outcome of the funding. Brad has every tool for this, and a great deal has already been moving in our favor. We do our part; the result isn't ours to grip.
You can name the one thing most slowing the company down — your biggest bottleneck — and you're actively removing it.
One person heroically patching a gap that's really a missing system or role; a bottleneck everyone complains about but no one owns.
The value we create is measured on the customer's side of the table, not ours. When the offer clearly helps a clinic make money, save time, reduce risk, or elevate its standing, the sale takes care of itself. Purpose first; revenue follows service.
The whole sales story sits on that ladder — show shipping cost up front so clinics protect their margin (make money), do the work instead of just digitizing it (save time), fewer rejections with a vet reviewing the AI (reduce risk), turn a dreaded favor into a service a clinic advertises (elevate status). We build for the founder's own earlier problem: pet travel that shouldn't have been this hard.
For anything you build, you can say — in the customer's own words — which rung it moves: helps them make money, save time, reduce risk, or elevate their status.
Feature lists that never name the customer's gain; selling status we can't yet deliver.
Excellence has a method, and the method has an order. Run these five steps in sequence on anything before it enters the roadmap. Doing them out of order is how a team locks in inefficiency and calls it progress.
Should this exist at all? Challenge the assumption before you optimize it — even a requirement from an expert.
Remove parts and steps aggressively; if one is truly critical it comes back on its own.
Refine what survives deletion — never polish something that should have been removed.
Shorten feedback loops — but only after the cleanup, or you just fail faster.
Automation scales what's already proven; automate too early and you make the inefficiency permanent.
The most common failure isn't running a step badly — it's skipping Step 1. When a constraint has become "just how it works," no one questions whether it should exist. Our live example: compliance coverage depending on a single person is the requirement to question, and "we'll figure it out" is the sound of Step 1 being skipped. The favorable read is real — it's only a bottleneck because the rest of the machine got efficient enough that one input now sets the pace. The fix is doctrine, not effort: name the constraint, give it an owner and a date, treat it like every other oath.
Distilled. If a new leader remembers nothing else, remember these.