Readiness is not about enthusiasm or budget. It is about whether your data is reachable, your processes are describable, and someone can say what a correct output looks like.
Sessions with the people who do the work today and the people who own the systems. We ask to see the actual screens and the actual exceptions, not the documented process.
Hands-on with a real sample. Frequently this is where a stated assumption meets reality — the field everyone relies on turns out to be free text, or only half-populated.
A document you can circulate internally: what is buildable now, what needs remediation first, what should not be built at all, with cost and effort ranges for each.
Then it has done its job, and it has done it for a fraction of the cost of finding out during a build. The output in that case is a remediation path: usually data access, evaluation capacity or a process that needs documenting before it can be automated. We would rather write that than take a build engagement we expect to stall.
It helps but is not required. If you arrive with a shortlist we assess those against feasibility and value. If you arrive with “we know we should be doing something”, the assessment includes use-case discovery — which usually surfaces candidates that are less exciting and considerably more valuable than the ones people arrive with.
The deliverable is written to stand alone and to be usable by another vendor. That is deliberate: an assessment whose conclusion is always “hire us” is not an assessment. We are willing to write an assessment recommending an off-the-shelf product, an internal hire, or doing nothing.
Someone who does the work today, someone who owns the systems, and someone who can speak to the constraints — typically security or legal. Three to five people, a few hours each. The most common cause of a weak assessment is only talking to management, because the documented process and the actual process differ in ways only practitioners know.
A few weeks and a fixed fee to know whether the thing you want to build is buildable — and what it would really take.
30-minute technical call · no deck
What we built, what stage it is at, and a link to the live thing wherever there is one.
yourOS is an operating system with an AI at its heart. You talk to it like a person, out loud or typed. It makes your calls, plans your days and works on your projects with a crew of agents, on your own private server. Our own product, built from the first commit; the waitlist is open.
Website, backend and app assets for Sonora, a free AI sound-therapy app on iOS and Android published by Cognitive AI.
Brand, website, prototype, apps on five platforms, the AI backend and the algorithm-intelligence pipeline for Podswap, a social growth engine that runs without a human in the loop.
In closed beta: Roxy, a private AI assistant with permanent memory running on infrastructure the user owns. Brand, site, product, backend and conversational design.
Live at coherence.com: brand identity generated with AI agents we directed, the motion system and website for the group behind Sonora, AboutAI, WakeUp and MudShadows. Agent work remains in build.
Live at domainbooth.com for DomainBooth, a premium domain brokerage: a new animated mark, every page redesigned and rebuilt with designed mobile layouts, and a custom CMS for its sales record, featured names, press and enquiries.
Apps, platforms and campaigns for these teams, long before the AI work. Every one is written up on the work page — what we did, and where our part ended.
