Run the business on one system.
Lenunu designs and runs the operating layer for your company: database, web and AI working as one connected system, instead of a pile of tools glued together. We architect it before we build it. Then we stay on to support it.
No pitch deck. No lock-in.
Sample data throughout. The interface cards on this page illustrate the kind of systems we build.
Most businesses run on tools that were never designed to work together.
The trouble is rarely one bad app. It is the handoffs between them: duplicated data, fragile syncs, and reports that live in one person’s head.
- Manual re-entry between systems
- Business data with no AI layer
- Databases cut off from the web
- Reports that take hours to compile
- Integrations that fail silently
There is a better way to build.
One connected system, built in three parts.
Build the system. Make it intelligent. Keep it running. Everything you need to run your systems, without the chaos.
Databases and web apps
We build new, or extend the database you already trust, with architecture meant to hold up for a decade. Then we put a fast web app on top of it, so the numbers are the same in the office and on site.
AI on your real business data
AI as a working layer in your operation, not a demo. Claude, OpenAI and Gemini sit in a thin layer you can swap without rebuilding the rest of the system.
Bridges and automation
Two-way bridges and APIs between your database and everything else. Workflow automation takes the re-typing out of everyday work. If it has an API, we can connect it.
Hosting, backups and monitoring
Hosting with a 99.9% uptime SLA, automated backups and monitoring. It runs on your infrastructure, a managed cloud or a hardened Linux server. Your choice.
Support from people who answer
Month to month, with no lock-in. Support covers monitoring, patch releases, small enhancements and an SLA for incident response. Your message goes straight to an engineer.
If it has an API, we can connect it.
We wire AI into the systems you already run: databases, cloud services and automation tools. These are the platforms we work with most.
- Database
- Claris FileMakerPostgresSupabase
- Web
- TypeScriptJavaScriptReactNode.jsViteAstroTailwind
- AI
- ClaudeOpenAIGemini
- Automation
- n8nNotionGoogle Sheets
- Hosting
- VercelCloudflare
Architected before it is built.
From a first call to a system in production, and what happens after.
-
Week 1
Discovery and architecture
A 30-minute call about your systems, your bottlenecks and what done looks like. Then we map the whole solution before writing code: data models, API contracts and integration points.
30-minute callFixed price after this step -
Weeks 2–6
Build
Two-week cycles. Each one ends with a working demo you can click, not a status update.
DemoDemoNext demo -
Launch
Deploy
Production launch on infrastructure you trust, with monitoring and documentation.
Live -
Ongoing
Support
We stay on after go-live. Month to month, with no lock-in.
Monitoring on
“Lenunu didn’t just build what we asked for. They built the operating system our team actually needed — AI, database, and automation working together without the daily friction.”
- years of database development
- 10+
- systems shipped
- 50+
- hosting uptime SLA
- 99.9%
- response time
- 24h
We run our own software, too.
Lenunu designs, builds and runs the systems companies depend on every day.
We also build and run our own product: BuilderHawk, a CRM for construction companies. Running our own software in production keeps us honest about what it takes to keep a system working after launch.
Quick answers.
How long does a typical project take?
Most projects ship in 6–12 weeks. Discovery and architecture take 1–2 weeks. Build runs in two-week cycles that you review at the end of each. Larger platform rewrites take longer, and we tell you what is realistic before you commit.
Do you work on existing systems or only new builds?
Both. About two thirds of our work is fixing, extending or modernising systems that already exist. We start with an audit, find what is brittle, and propose the smallest set of changes that gets you to a stable base.
How does AI fit into our existing workflow?
As a swappable layer on your real data. Typical jobs: turning unstructured notes into structured records, summarising long records, classifying inbound data and drafting outbound copy. The calls live in a thin service layer, so you can change providers without touching the rest of the system.
Where is our data hosted?
Your choice. We deploy to your existing infrastructure, a managed cloud (AWS, GCP or Hetzner) or a hardened Linux server. Sensitive workloads stay in your region with full audit logs. We don’t take custody of production data unless the contract says so.
How do you price projects?
Fixed-scope projects get a fixed price after the architecture phase. Open-ended platform work is a weekly retainer at a published rate. You see the scope, the budget and the milestones in writing before any code is written.
Do you offer support after launch?
Yes. Month to month, with no lock-in. Support covers monitoring, patch releases, small enhancements and an SLA for incident response. If you bring your own team online, we hand over the keys and step back.
Tell us what’s not talking to what.
Starting from scratch, or fixing a system that has grown past its limits? Either way, we’d like to hear about it.