Principles.
Good service comes from taking things away, not piling them on. These are our principles: five things we deliberately leave out, so the work that remains is the work that earns its place.
Most vendor websites list everything a vendor will say yes to, and that list only ever grows. We'd rather be clear about where our incentives stop and what we choose not to sell, because that's what makes the advice worth trusting.
We don't resell technology.
We sell our own. We refer the rest.
We don't resell technology.
We sell our own. We refer the rest.
Why it matters
Resale margin is the most common reason integrators recommend the wrong platform, tier, or add-on. We don't take it.
What this means in practice
When you need a platform, you buy it direct, and we'll help you get the best price straight from the supplier. We sell our own software and refer everything else. Where we have a commercial interest, we name it.
We don't recommend AI where it doesn't add value.
Including when declarative rules beat an LLM.
We don't recommend AI where it doesn't add value.
Including when declarative rules beat an LLM.
Why it matters
The most expensive thing in AI today is the project that went live, looked impressive, and didn't change anything operational.
What this means in practice
We'll tell you which category your job falls into (declarative, classical ML, generative, or hybrid) before recommending anything. If AI doesn't return value against handle time, cost to serve, customer effort, CSAT, or another metric you own, we say so, early, before you spend the budget. Not sure whether declarative rules or an LLM is the right fit? We'll work it out with you. See The Kanso Filter and Labs.
We don't build custom where native solves it.
Platform roadmaps move faster than custom code.
We don't build custom where native solves it.
Platform roadmaps move faster than custom code.
Why it matters
Custom code adds complexity your team carries afterwards, so it has to earn its place. Native features, when they arrive, are supported, documented, and included in the price you're already paying.
What this means in practice
If a native feature already solves your problem, we point you at it and don't sell you anything. If a feature is on the core vendor's published roadmap (Zendesk, AWS, Twilio, whichever platform you're on) we tell you and help you decide whether to wait. Custom is a considered choice, not a default.
We don't take on delivery without a measurable outcome.
Every engagement has a number.
We don't take on delivery without a measurable outcome.
Every engagement has a number.
Why it matters
Open-ended work ends with a slide deck and a handshake. Work with a defined outcome ends with something the business can check.
What this means in practice
Every delivery engagement carries one or more metrics you own, agreed with your sponsor and measured in your systems. A discovery call or first conversation is the exception: that's how we work out what the outcome should be. If we can't define it together, we won't start the build.
When we have a stake, we say so.
We partner with other technology companies, and we build our own.
When we have a stake, we say so.
We partner with other technology companies, and we build our own.
Why it matters
We work with technology partners and ship our own software, so sometimes the right answer is something we have an interest in.
What this means in practice
When it is, we say so, and we help you evaluate aligned alternatives so the choice is yours, tied to one or more metrics you own. We'd rather lose the sale than sell you the wrong solution.
Questions we get asked
What about things that aren't on this list?
Things not on this list aren't automatically in scope. This is a floor, not a ceiling. If you're unsure whether something fits, ask.
Has this list changed?
Last reviewed: June 2026. Any change will be noted here with the reason.
What if we ask you to do something on this list?
We'll decline politely and tell you why. The principles don't flex because an engagement would be lucrative.
Who owns these principles internally?
The founder, directly. The principles are instilled from day one, in the onboarding pack and reviewed in the quarterly operating review. Never further from the top than that.
If any of this sounds useful, here's where to start.
We fund two Maturity Mapping assessments per month. A senior practitioner spends real time on your problem, so we cap it at what we can do properly. Tell us where you're stuck in a few lines. We'll take the two we can help most this month, and point the rest to a better fit, or a faster route that isn't us.