What we know how to build
Every line is something we have already built and that runs today. Where a published case backs it, it links to it; where it does not, that is because we do not publish client names, not because it does not exist.
Agents and applied AI
-
A WhatsApp agent with human takeover
It answers straight away from a knowledge base, asks what is missing and books. Whoever runs it sees every conversation and can take it at any moment.
See the case -
Search by meaning
Queries against the database stop depending on someone typing the exact word.
See the case -
From conversation to tickets
A chain of agents takes the request in by chat, checks it is complete, validates every piece against the rules and turns it into work ready to run.
See the case -
An assistant over the user’s own data
It answers from the record of whoever is asking, with tools to query specific periods, and with outside text treated as data and never as instructions.
-
Agents with approval
The agents research, write and publish, and a person approves before anything goes out.
See the case -
Bots where your community already is
The same agent that answers on WhatsApp lives on Discord or in the site chat: the channel changes, the knowledge base and the rules do not.
-
Making every agent work the same way
Your team’s rules written as instructions any agent loads, so the result does not depend on who asked or which tool they used.
-
A bot that joins the meeting
It joins on Meet, Teams, Zoom or Slack, captures the audio and sends it on for processing, so the minutes do not depend on who remembered to take notes.
-
Generating in batches, reviewed first
Load the batch, see each piece’s spec and instruction before producing it, and download the lot at the end. Reviewing a thousand pieces one by one is not a plan.
Field operations
-
Evidence in the field
A QR scan at every step and delivery closed with a signature and a photo.
See the case -
A parcel’s whole life cycle
Waybill, pickup, distribution centre, route and delivery, with the in-between states reality demands: exception, rescheduled, returned.
See the case -
Routes, drivers and vehicles
Assigning parcels to a route, a driver console, and control of what each vehicle carries.
See the case -
Capture away from the office
The inspector’s app works on site and the file assembles itself without retyping.
See the case -
Addresses that validate themselves
A postal code catalogue so the address is fixed before the parcel leaves, not when it comes back.
See the case -
From finding to action plan
The inspection raises the finding, the finding opens a plan with an owner and a date, and the plan closes with the evidence that proves it. Nothing is left in an email.
See the case -
Booking with real coverage
Actual availability, blocked dates and the address checked against the area you truly serve, so nobody books a visit that cannot happen.
Systems talking to each other
-
An API so two systems can talk
When the system you already run does not expose what is needed, the interface gets built on top of it instead of replacing it.
-
Bulk load from a spreadsheet
The catalogue comes in whole from the file that already exists, validated first and with a report of what did not make it.
See the case -
One adapter per external service
Each network or provider comes in through its own adapter, so adding one does not touch what already works.
See the case -
Queues without installing a broker
Pending work lives in the database you already run, claimed with a lock so two workers never do the same job.
See the case
Identity and access
-
Sign in with an account or with Google
Sign-up, email verification, password recovery, and sessions listed so they can be closed from another device.
See the case -
Roles and permissions you can audit
Who can see and do what, written down as a matrix instead of scattered across conditionals, with a log of what happened.
-
Multi-tenant
Several accounts on one system, with data separation built into the design and not into a permission someone has to remember to set.
See the case -
Scopes that follow the org chart
Who sees what according to where they sit in the organisation, with the structure as data and not as a permission list someone maintains by hand.
-
A portal for your own customer
They sign in and look up their quotes, their invoices and the state of their business with you, without asking you by email.
Payments and invoicing
-
CFDI 4.0 invoicing
The invoice comes out of the same system that holds the catalogue, the customers and the quotes.
See the case -
Payments and tax data
A gateway, coupons with their usage history, and addresses carrying RFC and CFDI use ready to invoice.
See the case -
In-app subscriptions
Purchase and restore validated against the store, with payment details never passing through us.
See the case -
Different prices for different customers
Price lists per customer or per volume, applied on their own when quoting, which is where whoever keeps them in a separate sheet gets it wrong.
-
Contracts that renew and receivables that speak up
Recurring services with their renewal date, and the receivable that raises its hand before it is overdue, not after.
Security
-
Defence validation with synthetic attacks
Controlled exercises, versioned and signed, under human supervision and with a policy engine that has the last word.
See the case -
Scanning and remediation
Automated vulnerability detection and the pipelines that carry each finding to a fix, not to a report.
See the case -
Credentials that never leave the device
Encrypted with a key the phone itself generates, and on secure hardware not even root access extracts them.
See the case -
Getting ready for an audit
Leaving the evidence the way the assessing body asks for it, not the way it ended up in the shared folder.
See the case -
Checking the app before it ships
The package goes through a review pipeline with strictly ordered steps, to find what should not be inside before it reaches the store.
-
A console for whoever runs the defence
Launch the exercise, watch what happened step by step and keep the evidence, without depending on someone reading terminal output.
See the case
Mobile and desktop
-
Native where it counts
Kotlin modules under React Native, for the part that does not forgive a pause.
See the case -
It works with no signal
The app stores on the phone and keeps working when the network drops, which is when it matters most.
See the case -
Native desktop
One application for Linux, Windows and macOS when the work does not fit on a phone.
Content and publishing
-
A site that builds itself from what was approved
Publishing triggers the site rebuild, the newsletter and the alert, with nobody uploading anything by hand.
See the case -
Real time that persists
Websocket chat that is stored, and tournament brackets that advance on their own.
See the case -
Sites that generate and modify themselves
The site assembles from the business data, and later changes are applied as rule-driven pieces instead of hand-editing each file.
Documents and training
-
Document management with role control
The documents a process rests on, with who may see them, which version is current, and a trail of who touched what.
See the case -
Documents that generate themselves
Waybills, receipts and reports as PDFs, assembled from the system’s data instead of a template someone fills in.
See the case -
Online training
Courses with quizzes, per-person progress and a downloadable certificate of who passed what, for when training is part of compliance.
-
What expires says so in advance
Permits, certificates and contracts with their validity inside the system, warning ahead of time instead of turning up expired in an audit.
-
A handover you can run without us
Technical documentation, a database package and a backup guide, plus the repositories and the infrastructure in your name. If one day you want us out, you can.
-
Knowing what everyone is on
Team load and work progress in a single view, with tickets and pages that link to each other and an API so another system can read them.
Equipment on site
-
Charging through a physical terminal
The screen talks to the payment terminal over its own protocol, chip and contactless, and the state of the charge reaches whoever is standing there live, with polling as a fallback when the connection drops.
-
Machines that set themselves up
An installer leaves the machine in kiosk mode: system, dependencies, autologin, full screen and the application running, with no technician configuring by hand.
-
Fleet telemetry
Each machine reports its own state and that of its peripherals, so you know which one is down before the customer calls.
Data from other sources
-
Getting data from where there is no API
When the source offers no integration, the ingestion is built against whatever it does expose and served through an API of your own, stable even when theirs changes.
-
Detecting duplicate accounts and abuse
Comparing behaviour, not just declared data, to flag when two accounts are the same person.
-
Transcribing and translating audio and video
Upload the file, get the text, translate it and get it back as speech, with usage metered through credits and plans.
If any of this looks like your problem
Tell us which one. The first call is for finding out whether this applies to your case or whether we are selling you something you do not need.
Tell us about your project