No gatekeepers
Your message lands straight with the people who will talk to you — no form, no sales triage.
LLMU2Software House
From the first commit
to production.
We design, build and maintain the software your operation runs on every day.
A small company on purpose.
LLMU started with four people who had built software inside companies large enough to understand exactly why they move slowly. We built the company we would have wanted to hire: a small team, senior from end to end, that gets into the problem alongside the client and leaves only once what was agreed is running in production.
There is no management layer between you and the people writing the code. The four people you meet on the first call are the same four who deliver the project.
$ whoamillmu — software house$ llmu --helpusage: llmu <command> build web and mobile products connect integrations and APIs review technical advisory$ llmu statusTaking on new projects.What we build
Four areas of work. In all of them we hand over code that stays standing after we leave.
Web products
Dashboards, portals and internal systems your team opens every day, built to hold up under real use.
Mobile apps
iOS and Android from a single codebase, without giving up what people expect from a native app.
Integrations and APIs
We connect the systems already running your operation so it stops depending on spreadsheets and manual copying.
Technical advisory
Architecture review, performance diagnosis and an execution plan your own team can carry out.
How we work
Four stages, in this order, on every project. You always know which one we are in.
- 01
Discovery
We learn the problem, map the real constraints and decide what is worth building first.
- 02
Architecture
We design the solution and agree on scope, timeline and cost before the first line of code.
- 03
Development
Two-week cycles, each one ending in something you can open, test and comment on.
- 04
Launch and support
We ship to production, stay through the first months and document everything before handing over.
Who builds it
Four partners. Three on the code, one on scope and schedule. All of them talk to clients.
Works on web products and the integrations that connect them to the rest of the operation. Tends to take on legacy code, work out how it got that way, and hand back something the next person can maintain.
- Front-end
- APIs
- Legacy
Works on the back of the applications: data modelling, services, and the shape of the APIs the rest of the team consumes. Cares about what happens when volume grows and the happy path stops being the only one.
- Back-end
- Data
- APIs
Builds the mobile applications and the interfaces that reach the end user. Works close to what is visible: what people tap, how long they wait, and what happens when the connection drops.
- Mobile
- Front-end
- Interface
Looks after scope, schedule, and the conversation that keeps those two honest. Translates what a client needs into something the team can build, and says early when the numbers do not add up.
- Delivery
- Planning
- Clients
What we have delivered
The commercial projects we have delivered so far.
Flow Analytics
Business management software
Analytics app for Flow's management ecosystem, which brings sales, inventory and finance together in one place.
flowanalytics.com.brSocomec Brasil
Critical power infrastructure
Control panel for the Brazilian operation of Socomec, a maker of UPS systems and transfer switches.
br-socomec.com
Let's talk
▌
Replying takes less time than writing a brief. Send a message and we will set up a 30-minute call, no strings attached.
contato@llmu.com.br
After you hit send
A 30-minute call
You describe the problem; we hand back what we can already see from here.
A clear next step
Scope, timeline and cost — or an honest “we are not the right fit”.