We remove the manual work that scales badly — and hand over systems you own, not rent.
Most automation work fails in the scoping, not the building. We take the operating reality seriously, and build systems that are still running in year three.
Scope first. Architecture second. Implementation is the last 40% — and the easiest part.
Documented and handed over on your own infrastructure. No lock-in, no rental relationships disguised as software.
Claude, GPT, local models. Cost, latency, and failure modes designed in — not patched on afterwards.
Engagements typically combine two or three of the below. We scope the combination to the problem, not the other way around.
Manual work removed, not streamlined. Lead capture, invoicing, reconciliation, multi-location sync.
Production agents for research, drafting, and structured judgement — built with cost and latency in the spec.
Scrape, ingest, normalise, sync. Supabase-to-anything — queryable by your team without asking us.
Lead routing, deal hygiene, drafted outreach. Less of the work your sales team does that isn't selling.
Vendor/Seller Central, flat files, pricing engines, multi-channel sync. Five years in the toolkit.
WhatsApp, email, voice. Booking, triage, after-hours capture — deployed where your customers already are.
Every engagement follows the same shape: diagnose the real process, architect, build on your infrastructure, hand over. Systems built this way are still running when we're long gone.
Client names are withheld by default; descriptors tell you the sector and shape of the work. Two of the four are composites of recurring engagements — flagged where they appear.
A specialist distribution group — tens of thousands of SKUs, tiered pricing, weekly pricelist runs — was building customer-specific pricelists by hand from SAP exports reconciled in spreadsheets. The internal view was that automation wouldn't work because of the edge cases.
We built a Python pipeline that resolves customer-level pricing logic against the account matrix and delivers a finished pricelist. Eighty-plus edge cases handled explicitly, not papered over.
A consumer-facing directory in the wedding vertical needed to go from empty CMS to thousands of vetted vendor listings across multiple European cities — without hand-curation or a content team.
We built the full pipeline: scraping and enrichment from public sources, deduplication and quality-scoring in Supabase, AI-generated copy gated by rule-based validation, and a two-way sync into Webflow's CMS with publish state controlled from the database.
A recurring pattern: a multi-location service business where each site tracks leads, bookings, and revenue slightly differently. Head office assembles a weekly report by chasing spreadsheets — often a week old and occasionally wrong.
The intervention shape is consistent: a central CRM strict enough that location managers can't go off-script, ingestion from whatever each site already uses, and a reporting layer head office can trust. What changes visibly is the Monday morning. Composite of recurring multi-site engagements.
A recurring engagement across real estate, professional services, and B2B: the pipeline is the bottleneck, but the founder is the only person who can judge which leads are worth their time. We build a private lead infrastructure — targeted signal sources, Claude-based rating tuned on past wins, and a private mobile feed that surfaces only leads worth acting on.
The founder stays in the loop for every message sent. Volume stays low; quality stays under their control. The bottleneck was never message volume — it was attention. Composite of recurring founder-led engagements.
Every engagement is scoped individually. The shape below describes the kind of work — the specifics come from a conversation.
For when you know something's broken but don't yet know where. We map the operating reality, surface the interventions with the best return, and hand back a written brief.
A specific workflow, agent, or pipeline — scoped, built, handed over, documented. The most common way clients work with us. Care retainer optional.
Ongoing arrangement. One or two days a week inside the business — spotting the right work before it's asked for, and executing. For clients we've already delivered for.
An MBA in data science. More than fifty engagements delivered across Europe, the UK, and North America — spanning automation builds, operational strategy, and marketplace growth for clients from five-person studios to mid-market operators. Full-time on automation since 2024.
Operating from London and Vienna. Native German, working English. Executive MBA, Imperial College London. We take a small number of clients at a time.
Describe the operating problem you're trying to solve. We'll tell you honestly whether we can help, roughly how the engagement would look, and whether we have capacity this quarter. If we're not the right fit, we'll say so in the call.