What we do

Technology and systems

We build the systems the diagnosis points to: websites and online stores, management platforms, integrations between the systems a company already uses, and software that does work people are doing by hand today, such as reading and validating documents, chasing invoices, triaging requests, pricing and reporting.

Where it makes sense, these systems are built with AI. A central orchestrator reads what comes in, decides what it is, and hands it to the agent that handles that case. The person stays in the loop for exceptions and approvals, and the system logs every decision so it can be audited.

What we build

Websites and online stores

When the site is part of the commercial process, connected to stock, payments and CRM

API integrations

Between ERP, CRM, ecommerce, invoicing and the other systems that do not talk to each other today

Management platforms

When the operation is running on spreadsheets

Document intake and validation

Data extraction and checks against your own rules

Invoice and receipt collection

Reconciliation and chasing

Request triage and routing

From email, forms or a portal

Pricing and margin tools

With competitor and cost monitoring

Reporting

Dashboards that read the source data instead of being assembled by hand

AI systems

Systems built with AI

Agents and AI systems that read documents, answer and route requests, and run repetitive processes, with people approving the exceptions and every decision logged. On the AI systems page we explain how we build them and where they are already running.

See AI systems

Platforms and tools

We build on the platforms the company already uses, or on the ones that best fit the problem, AI included. The system can run in the client’s own environment, in our cloud, or on a server inside the company.

The choice is made in the diagnosis, based on security, cost and who maintains it afterwards.

Microsoft 365CopilotPower PlatformGoogle WorkspaceGoogle CloudSalesforceHubSpotn8nOpenAIClaudeClaude CodeGeminiGrokOpenRouterCodex

Delivery and maintenance

Scope and timing are defined in the diagnosis, for each system, based on how many sources it reads and how many rules it has to respect. After go-live there is a monthly fee for maintenance and changes, charged on hours used, because a system that nobody maintains stops being used within a year.

The people who will use it take part in the build. Teams that have worked the same way for twenty years need time to change how they work, so change management is part of the project from the start.

Start with the diagnosis
A free first conversation about one concrete challenge, ending with a written summary of what we found. No commitment beyond that conversation.
Talk to a specialist