Frontend
Design-system migrations and component work, one pull request at a time.
Custom services
Roles, playbooks and gates carry every process in which work recurs. In software development the agents stand ready; every further area is built from the same building blocks.
Ticket in, reviewed pull request out. A PM, a developer, a review and a QA agent work as a team, around the clock, beside your developers.
Gate: a senior review, and your approval before the merge
The ready agents, by field
Design-system migrations and component work, one pull request at a time.
API versions, dependency upgrades and the test backfill nobody has time for.
A regression pass on every release, reported in the ticket.
Pipelines, runners and infrastructure changes, each behind a review.
Schema migrations and pipeline checks that run before anyone asks.
Docs that follow the code, updated with every merge.
Dependency and secret scans every night, with the fix as a pull request.
Evidence collected as the work happens, ready when the auditor asks.
Qualify incoming enquiries, draft quotes from the product catalogue and the customer history, prepare the follow-ups for the key account.
Gate: no quote goes out without approval
The roles in this playbook
Reads every incoming enquiry, scores it against your criteria and routes it to the right person.
Drafts the quote from the product catalogue and the customer’s history, ready for approval.
Prepares the key account’s follow-ups: what was promised, what is open, what comes next.
Writes every contact and every step back into the CRM, so the record is complete.
Classify requests, resolve the standard cases, and hand complaints to the right place with every document attached. A person gets the rest, with the full context.
Gate: answers to customers are checked before they are sent
The roles in this playbook
Classifies every request and sends it where it belongs, with the customer’s history attached.
Resolves the recurring cases; the answer is drafted for a check before it goes out.
Hands a complaint to the right place with every document attached, ready to act on.
Everything else goes to a person, with the full context and a suggested answer.
Read orders from fax, mail, letter and phone and check them against the ERP. Match invoices with the order and the delivery note. Read contracts for deadlines and clauses.
Gate: postings in the ERP only after a person approves
The roles in this playbook
Reads orders from fax, mail, letter and phone and checks them against the ERP.
Matches every invoice with its order and its delivery note, and flags what does not add up.
Reads contracts for deadlines and clauses and puts them where the team sees them in time.
Prepares every posting for the ERP; a person approves before it is booked.
Bundle supplier enquiries, reconcile confirmations and delivery times, and report deviations before they reach production.
Gate: orders above a threshold go to a person
The roles in this playbook
Bundles the enquiries and sends them out, one per supplier, with the specification attached.
Reconciles order confirmations and delivery times with what was ordered.
Reports a deviation before it reaches production: late, short, or not what was ordered.
Places the routine orders; above the threshold a person decides.
Answer questions against SharePoint, mail and documentation, onboard new colleagues, prepare the research for specialist teams.
Gate: answers name their source, and what is uncertain is marked as such
The roles in this playbook
Answers questions against SharePoint, mail and the documentation, and names where the answer comes from.
Walks a new colleague through what they need to know, in the right order, with the right documents.
Prepares the research for a specialist team: what is known, where it stands, what is uncertain.
Finds what the questions show is missing and drafts the page that answers it.
What recurs at your company, is manual and costs time. If the flow can be described, a playbook can be built from it.
Gate: we set it together, before the first run starts
Your process is not here? Bring it with you: in a first meeting we find the right starting point together. Book a first meeting
We come to you, understand your processes and work out with you the use cases with the biggest lever. Then we build them pragmatically, cut to your day-to-day, so your team uses them from day one and the value shows within weeks.
We come to you, listen and get to know your processes.
Together we identify the levers with the biggest potential and prioritise them by effort and value.
The solution is cut to your processes. Fast, lean, ready to use.
Weeks instead of months, with a clearly quantified return. Results in daily operations, not concept papers.
After every phase you decide how it goes on, and whether. No long commitments, no risk of a concept paper.
We come to you, understand your processes and together prioritise the use cases with the biggest lever.
Result: An AI potential report and prioritised use cases
gate ‖ you decideThe scan becomes real. We design the architecture, choose the right tools and build a working prototype on the real process.
Result: A working MVP and a clear decision on scaling
gate ‖ you decideFrom the prototype to the production system. Integration, security, handover to your team.
Result: A production system, an enabled team, an ongoing partnership
gate ‖ you decideHosting, updates and further development, so you use the system for the long run.
Result: The system runs, is maintained and keeps evolving
After the potential scan, one to two weeks, you know exactly where the lever is. A first working MVP typically takes one to six weeks, testable on your real data. Only then do you decide on build and rollout.
Yes. That is exactly what phase three, build and rollout, is for: ERP, CRM, SharePoint, e-mail and file shares are the standard connections. In the scan we check what is technically feasible before you commit to anything.
Hosting in your cloud or in ours, both GDPR-compliant. Which models are used, OpenAI, Anthropic or open-source models on premise, we decide together, depending on how sensitive the data is. Compliance is part of phase three, not an add-on.
No, we are tool-agnostic. OpenAI, Anthropic, open-source models on premise or a combination: the choice follows the use case, the data-protection requirements and the cost, not hype or commission. We hold no stake in any vendor and have no reason to push you into an ecosystem.
We deliver working systems, not concept papers. We come from building: our own software products, our own agents in production. The result of every phase is something you can use, not a slide deck.
Every phase is booked on its own and closes on its own. After each phase you decide whether it goes on. No annual contracts, no hidden terms.
Then we say so. The potential scan is open-ended by design. We only recommend what we would build ourselves. Better an honest no-go than a pilot without substance.
A first meeting takes 30 minutes. Afterwards you know whether we fit, and where your biggest lever is.