What we know, in writing.
Articles, documented cases, the technology we build with and answers to what clients ask before starting a project.
Does your operation need a system yet?
Check what happens in your company today. It is not a test and we ask for no data: it is a quick way to see whether the cost of not having a system is already showing.
- 8 questions
- 2 minutes
- No personal data
Use cases, with measured results.
Each case covers the challenge, the technical solution and what changed in the team’s daily work.
See all projects- Applied artificial intelligenceAI vehicle damage inspection & claims analysisInsurance & Fleet Logistics ProviderBefore: 48 hNow: 15 sper vehicle assessment11,520× less timeRead case
- Automation & integrationsEnterprise API integration & sync middleware hubWholesale Distribution EnterpriseBefore: 6 hNow: 3 sper order, portal to ERP7,200× less timeRead case
- CRM & management systemsCorporate event management CRM & deal pipelineCorporate Events Production AgencyBefore: 72 hNow: 15 minto build a quote288× less timeRead case
- Web & mobile developmentOffline-first mobile app for field techniciansIndustrial Maintenance ContractorBefore: 12 daysNow: 24 hto bill a field service12× less timeRead case
- Custom softwareEnd-to-end auto repair shop management systemAutomotive Service ChainBefore: 100%Now: 25%of the time to issue quotes and orders75% less timeRead case
Logarithmic scale: each axis mark is 60 or 24 times the previous one.
How we work, in four stages.
Every project goes through the same four stages, with something concrete you get at each one.
- MapHow you work today, drawn with you.
- BlueprintWhat we will build, approved by you.
- BuildIn stages, checked against the blueprint.
- OperationGo-live, adjustments and improvements.
No jargon
The words you will hear in a project, explained the way we would explain them in a meeting.
- Operation map
- A drawing of how your company works today: who does what, where work comes in and where time is lost.
- System blueprint (SRS)
- The document that says what the system will do, who uses it and what it connects to. It is approved before any code and it is yours.
- Module
- A part of the system that solves one specific task, such as orders, inventory or invoicing.
- Integration
- Making two systems pass information to each other on their own, with no copy and paste.
- API
- The door through which one system asks for or hands data to another, securely.
- Test environment
- A copy of the system where you review each version before it reaches your team.
- Cloud
- Servers outside your office: the system works from anywhere, with backups.
- Source code
- The instructions the system is made of. If it is yours, you can switch vendors without starting over.
What we write, sorted into lines.
We write about what we see in our clients’ operations: what to automate, when to build and how to avoid common mistakes.
- OperationsNextHow to tell when your operation needs a system1 in progress
- Use caseNextFrom spreadsheets to a connected repair shop1 in progress
- MethodNextWhat a system blueprint is and why it should be yours1 in progress
- Applied AINextWhere AI actually helps a small business, and where it doesn’t1 in progress
The stack we build with.
Modern, typed, production-tested tools. We choose the combination based on your operation, not on trends.
- Web & frontendWhat your team sees and uses
Astro
React
TypeScript
JavaScript
- BackendYour business rules
Node.js
Python
.NET
Java
- DataWhere your information lives
PostgreSQL
MySQL
SQLite
Supabase
Firebase
- MobileThe system in your pocket
Flutter
Dart
Kotlin
- CloudWhere it all runs
AWS
Applied AI: the right model for each task.
We don’t tie your system to one vendor. We connect the model that best solves each part of the process.
- Reading documents
- Sorting requests
- Answering customers
- Detecting damage in images
OpenAIGPT · Whisper
ClaudeAnthropic
GeminiGoogle
DeepSeekR1 · V3
MistralMistral AI
LlamaMeta
QwenAlibaba
Hugging FaceOpen models
OllamaLocal models
LangChainOrchestration
n8nAutomation
PerplexityAI search
Frequently asked questions
Sorted by the moment of the project when they usually come up.
Before starting
How long does a project take?
It depends on scope. A first working module is usually ready within a few weeks, and from there we deliver progress every 1 to 2 weeks for your team to try.
How do we get started?
You walk us through your process on a call. We analyze your case and send a concrete proposal with no commitment.
During the project
Do I own the code?
Yes. The repository, credentials and databases belong to your company from day one. No vendor lock-in.
Can you connect with the tools we already use?
Yes. We integrate ERPs, electronic invoicing, payment gateways, WhatsApp and existing spreadsheets so you don’t start from scratch.
After launch
What happens after launch?
We stay with you through preventive monitoring, support and adjustments as your processes change.
Didn’t find your answer?Ask us directly
Tell us what's slowing your operation down.
You don't need to know which technology you need. Tell us how you work today and we'll design the next step.
Tell us your processAfter you write to us
- We replyWithin 24 business hours.
- We talk for 30 minutesA call to understand your operation.
- You get a proposalWith scope and stages, no commitment.