Expertise
Strategy that ends in a scope you can build from
What we sell here is a two-to-three week discovery, run by the same senior people who would build the thing, ending in a scope, an architecture and a cost you can act on. On AI work that discovery is also where success gets written down precisely enough to score. Preetham Reddy started the company on the difference between filling a seat and owning the problem, and that is still how we staff it. If a deck is what your board needs, we will write one, but the useful artefact is the scope underneath it.
Strategy that ends in a scope you can build from.
What we build
- Discovery run by the people who will write the code
- A written scope and a realistic cost before a larger commitment
- On AI work, a scoring rubric as a first artefact
- A recommendation to not proceed, when that is the honest one
How this is delivered
Forward-deployed teams
Product, design and engineering people who sit inside your business, find the real problem, and ship it.
FAQ
Questions we get asked
Do you do digital transformation strategy?
Yes, in the form that tends to be useful. We sit with you for two to three weeks and come back with something you can build, or a reason not to. How that engagement runs is on /how-we-work.
Who is in the first conversation?
A senior engineer. Often Troy Busot, our CTO. On product questions, Andrew Ripley. There is no account layer between that conversation and the people who do the work. The model is /services/forward-deployed.
What if discovery says we should not hire you?
Then that is the finding. Preetham's line is that we would rather tell a client in March they have two weeks of work they can do themselves than bill them for six months of finding that out.
Tell us what is stuck.
A conversation with an engineer. If two weeks of discovery is the honest start, that is what we will sell you.