01
Product build
From idea to something people can pay for
We scope it, design it, build it and put it live. First release in weeks, not quarters, because the scope is deliberately narrow. Then we keep going with real user data instead of guesses.
Software you can put in front of paying customers.
A founder on every project, start to finish. We design and build web and mobile products for teams that need the real thing, and we stay on them long after launch.
Fifteen minutes with one of the founders. Not ready for a call? Send two lines instead.
Clients we have worked with
Why this is different now
Getting to a demo stopped being the hard part.
A founder with an afternoon and a Lovable subscription has a clickable prototype by dinner. That part is solved, and it's not coming back.
What still breaks is everything after. The data model that worked with twelve records and falls over at twelve thousand. Auth that shows the wrong user someone else's invoices. The integration with an ERP nobody documented. Payments failing on a Saturday, and no one to call.
We write code with AI too, and it makes us faster. It doesn't make the decisions. Architecture, design, review and deploy are done by people, and that is the part you are actually paying for. The typing got cheap. The judgement didn't.
What we do
Four ways we get involved.
02
AI inside your product
Agents, copilots, search over your own data
The part your team hasn't had time to figure out. We build it into the product you already have, not as a separate toy that nobody opens twice.
03
Prototype to production
You built it with AI. Now it has to hold.
Someone on your team shipped something with Cursor or v0 and it works in the demo. We take it from there: data model, security, integrations, deploy, the parts that decide whether it survives the first hundred real users.
04
Ongoing product work
The months after go-live
Most of our projects don't end at go-live. On average, clients keep us for about a year and a half after the first release. Monthly retainer, three-month minimum.
Selected work
Products that have been live for years.
We do not have a growth chart to show you. What we have is how long each of these stayed ours, and on average that is a year and a half.
PlayerPulse
Sports performance
A proprietary performance metric built on years of research and millions of data points.
- Built
- Mobile app, backend, infrastructure
- Working together
- 3 years, still going
SplitInk
Shared expenses
Splitting a bill with friends, then actually getting paid back through whichever app they already use.
- Built
- UI/UX, mobile app, backend, infrastructure, branding
- Working together
- 2 years
Municipalities Platform
Public sector
Data and services for local councils: risk mapping, analysis and the reporting that has to go out on time.
- Built
- UI/UX, mobile app, backend, infrastructure, branding
- Working together
- 1 year
Clients
People who kept us around.
Read the durations under the names. Nobody keeps a studio around for years out of politeness.
“Their project management was great. They were really helpful and professional.”
Fabrizio Martino
CEO
Mobile App Dev for Drug Delivery Platform · 18 Months
“They were fast, worked hard, and responded to change quickly.”
Travis James
CTO
Mobile App Dev for Healthcare Company · 6 Months
Our process
Five phases, every time.
- 01
Scoping
One week. We work out what's in the first version and what waits.
- 02
Design
Screens before code, so you see it before you pay for it.
- 03
Build
AI-assisted, reviewed by people, deployed continuously.
- 04
Review
You use it before anyone else does, and we fix what's wrong.
- 05
Live, then keep going
Go-live isn't the end of the project for most of our clients.
How a project starts
You get a fixed price before you commit to anything.
We don't quote from a brief. Fixed-price work without a written spec is how agencies end up building for free for three weeks, then asking for more money halfway through.
So every project starts with a scoping week. One week of real work that gives you the architecture, the functional spec, a phased plan and a locked price. It costs €1,500 and it comes off the first phase if we build it.
The document is yours either way. If you take it to another studio, that's fine. It means the week did its job.
We are not booked out. A scoping week can start as soon as next Monday.
€1,500
Scoping week, deducted from phase one
2 weeks
Typical first release, once the scope is locked
3 years
Our longest running engagement, still going
Straight talk
When we're the wrong choice.
- You want developers by the hour sitting inside your team. We build products, we don't rent people.
- The budget for the first phase is under €10,000.
- It has to be live in two weeks and the scope isn't written down anywhere.
- The person who actually decides isn't going to be in the conversation.
If one of those is you, put it in the first email and we'll tell you straight away. A fast no is worth more than a slow maybe.
Who answers
Write to us and a founder replies.
Not an account manager and not a sales team. A founder oversees your project from the first call to the last deploy, and the team around them grows or shrinks with what the build needs.
Luca Iaconelli
Co-Founder, Senior Full-Stack Architect & Engineer
Umberto Grimaldi
Co-Founder, Senior Mobile Architect & Engineer
Before you ask
The questions we always get.
There is no price list, because the same two weeks of calendar can mean two very different projects. We quote in euro, and the scoping week costs €1,500 and turns the question into one number you can put in a budget. Below €10,000 for the first phase we are the wrong studio, and we will say so before you spend anything.
Two founders and the team that builds with us. The architecture, the design decisions and the reviews stay with a founder on every project, and the team grows or shrinks with what the build actually needs. What you never get is a senior in the pitch and a junior left alone on the project.
You do. We hand over the source and you own it.
AI speeds up writing code. It does not make the decisions. Architecture, design, review and deploy are done by people. Judge the result, not the method: the work is on this site, and so is how long each client kept us afterwards.
Screens in the first days, and a first release you can click through in weeks rather than quarters. That only works because the scope is narrow on purpose. Most of the projects we are still on today started exactly like that.
The code is yours and nothing ties you to us. Most clients stay because it's faster, not because they have to.
That makes sense once the product is validated. Before then, hiring means two or three months of recruiting plus a fixed cost while you're still finding out whether you're building the right thing.
Contact
Tell us what you're building.
A couple of lines is enough to start. You'll hear back from Luca or Umberto, not from a sales team.
Usually you get an answer the same working day. And if it isn't a fit we'll say so in that first reply, instead of booking you into a call to find out.
Prefer to talk?
Or email us
hello@iglu.dev