Technical Strategy & Consulting
A second opinion from people who build: before a large decision, in the middle of a hard one, or when nobody on the team has done this before.
Advice is cheap to give and expensive to follow, so ours comes written down, with the reasoning and the trade-offs, and sized to what your team can actually carry out.
Because we also build and operate software, the recommendation is one we would be willing to implement ourselves.
What we take on
Architecture reviews
An independent read of a design before it is built, or of a system that has stopped scaling.
Technology selection
Build or buy, which framework, which cloud: a recommendation with the reasoning on paper.
AI readiness assessments
Where AI would pay for itself in your business, where it would not, and what data you would need first.
Technical roadmaps
What to do in what order, with rough cost and risk for each step.
How an engagement runs
Scope
A conversation, then a short written plan: what gets done first, what it costs, and what is deliberately left out.
Build
Working results early and often. You see progress in something running, not in status reports.
Ship
Deployment, monitoring and backups are part of the job, not an afterthought.
Hand over
Your code, your accounts, and documentation written for whoever maintains it next.
What we use
Work that backs this up
What we recommend, we have also built: a product in production and an open-source numerical engine.
Inventyl
Camera-first inventory for small business
An installable web app for shops that have outgrown spreadsheets: scan barcodes to take stock, photograph a supplier invoice to restock, and keep counting when the connection drops.
OpenBLUP
A statistics engine for plant and animal breeding
A linear mixed model engine in Rust, with Python bindings, a command-line tool and a browser app that runs the whole engine as WebAssembly.