Framing workshop
Five working days. We leave you a recommendation: build, wait, or narrow the problem, plus the risks we would not ignore.
Services
Software for decisions and shared records.
Pick a practice, or describe the product and we will tell you which parts you actually need. A written estimate follows a framing call.
Practice
Applied AI
We put models to work on a defined job: reading a packet of documents, ranking a queue, drafting a reply, or watching a metric. The interface, the evaluation, and the override belong in the same release.
- A written task, a success metric, and the cases that must never pass quietly.
- A frozen evaluation set your team can rerun after each change.
- Integration behind your own product, with logging and a rollback path.
- Agent workflows limited to an allow-list of tools.
- A review screen for low-confidence or high-impact items.
Practice
Blockchain systems
We design the smallest ledger surface that does the job, then the tools around it. Contracts without an operator console tend to stall the first time someone needs to pause or rotate a role.
- A network choice and a short note on what should not go on-chain.
- Contract design, tests, and an upgrade or migration path.
- Wallet and permission flows. Production keys stay with you.
- An indexer and an operator console for roles, pauses, and reads.
- A deployment runbook and checks for the first weeks live.
Practice
Joined products
Some products need a model and a ledger in one path. We build that when several parties must agree on what was proposed, what was approved, and what was recorded.
- A proposal object: the fields a model is allowed to fill.
- A policy gate: thresholds, rules, and a named human approver.
- An anchor: a hash or transaction on the ledger you choose.
- A replay view so a reviewer can reconstruct the record later.
Shapes
How an engagement is packaged.
Each shape has a written outcome. You decide whether the next one is worth doing.
Prototype
Two to four weeks. A clickable slice and the test that tells you if a full build is justified.
Build
Scoped releases with acceptance tests. Milestones are short enough that a wrong turn is cheap to correct.
Stewardship
A named pair after launch for incidents, evaluation refreshes, and small contract or model changes.
Not sure which practice fits?
Send a short note. We will answer with the smallest engagement that could test the idea.