What if someone had already solved that problem?
re:boot builds up domain knowledge by industry and workflow with every AX project. Find cases close to your industry and your work, and what we learned along the way.
Cases by industry and workflow
Clients are named only by industry and size. The demo uses a fictional company and no real customer data.
Twelve business areas in one system: 225 features in 16 weeks
Global automotive parts maker · Program management and profitability analysis system · AI-Native Development · Build
Over 500 requirements delivered, with AI driving each one from requirement to release and record — 700+ screens and about 3,000 APIs.
Vibe coding end to end · VIBE OPS methodology · Ops CLI for VIBE OPS
Read the caseFrom a daily flood of news to AI reports on the topics you follow
Major card company · Trend news sensing portal · AI service · Build
A research flow — choose topics, analyse news, get reports, receive alerts — built into an AI portal connected to the company's SSO, email and messenger.
Generative AI · Corporate SSO · Groupware alerts
Read the caseBooking rules dug out of legacy code and moved behind APIs
Golf booking platform · Platform rebuild · AI-Ready Platform · Build
AI found and documented booking and group-join rules scattered across old screens and SQL, and the platform was rebuilt around APIs that AI agents and other services can call.
Legacy rule extraction · API architecture · Per-repo AI rules
Read the caseTwelve manual entries become one request and one approval
re:boot Agent · Fictional company demo · No real customer data · B2B services (fictional) · AI Workflow · Demo
Procedures live in skills, execution stays in existing systems. Contract → activation → billing with one natural-language request and one human approval.
Skills · CLI · API · Human approval
Read the caseEvery case makes the next AX project faster
A finished project leaves more than a system. It leaves domain knowledge — the rules and procedures of the work — and the next project in the same industry and workflow starts from there.
- Work on the ground
- Captured as domain knowledge
- Redesigned for AI to do the work
- Built and run
- Starting point for the next project
Where our domain knowledge runs deep
AX starts from the work, not the industry. Where our founder and team have worked before, we start faster with the domain knowledge we already have.
Manufacturing
Orders, cost, profitability, quality, schedules
Finance & fintech
Cards · loan brokerage · MyData
Commerce
Luxury · cross-border · pre-owned luxury · official IP merch stores
Games
Global portal · mobile games · H5 games
Advertising & rewards
Ad monetization platform
Leisure & booking
Lodging · golf booking
Not on the list? That's fine. The on-site assessment starts by finding where the rules of your workflow actually live.
Recent posts
- · Development AXAX Field Notes: sixteen weeks of rearranging the order of workStarting from AI added on top of unchanged work: how we handed a whole requirement to AI agents, sixteen weeks in numbers, boundaries and rules, people's working day, and where your company could begin, in one piece.
- · AXOpsA project operations system AI agents use directly: connecting VIBE OPS with a CLI and SkillsRules live on the server, the integration is one thin CLI, and the order of work and where to stop live in procedure documents (Skills). A technical look at how far the agent goes and where it hands over to a person.
- · Platform AXWhat is an AI agent?Acting on someone's behalf, a loop, and the next stage of work. We define AI agents both by what the word means and by how they are built, and set out what to weigh when you bring one into your work.
Would this work for us? Find out with a free two-week on-site diagnosis
Pick one workflow and we'll diagnose it on site for two weeks, then hand you a report and a build proposal. No obligation to go further.