Software development
We build the product and we also take responsibility for what comes after: that another team can understand it, that it can be changed without breaking, and that it doesn't depend on us to keep existing.
Who it's for
- You need something custom because what's on the market doesn't match how you actually work.
- You have a system that works but nobody dares to touch any more.
- You're coming from a development that stalled halfway and has to be resumed or redone.
- You want to start from scratch with the technical decision made properly from day one.
What's included
Web applications
From sites that live on search visibility to complex internal panels. The architecture is decided by the problem, not by fashion.
Mobile applications
A single codebase for iOS and Android whenever the project allows it, which is almost always. Lower cost to build and to maintain.
Admin panels
So you manage your own content and your own data without depending on us for every change.
Integrations
Connection with the systems you already use: billing, payments, authentication, internal services.
Maintainable code
Written to be read by a person, not just to compile, with the minimum documentation another team needs to pick it up without doing archaeology.
Deployment and go-live
We leave the product running in a real environment, with the processes to update it without drama.
How we approach development
Development starts once the problem is understood, not before.
Define
Technical and functional scope in writing: what gets built, with which technology, and why that one and not another. This is where the expensive-to-change decisions get made.
Build
We move forward in usable pieces, not one block that appears at the end. You can see and test the product as it grows.
Deliver
Go-live, documentation and handover. The code and the access are yours from day one.
A real case
Health management and prevention platform
A private application for patients and professionals, entirely behind authentication. Since it doesn't rely on search engines to reach its users, the weight of the technical decision went entirely to the experience of using it: records, follow-ups and constantly changing states. It was built in React, prioritising interaction fluidity over server rendering, which added nothing in this case.
Frequently asked questions
- Which technologies do you work with?
- Whichever suits each project. We've built in React, Next.js, AngularJS and Ionic, and the choice comes from what the product needs: whether it depends on search engines, whether it's private, whether it needs a mobile app. Always reaching for the same tool is comfortable for the developer and expensive for the client.
- Is the code ours?
- Yes. The repository, the access and the infrastructure are yours from day one. We don't work with arrangements that leave the client tied to the supplier.
- Can you take over a project another team left behind?
- Yes, but we review the code first and give you an honest opinion. Sometimes resuming is right and sometimes it costs more than rebuilding. Either way we tell you before starting, not halfway through.
- What happens after delivery?
- We can stay on for maintenance and evolution, or hand over to your team. What we don't do is leave the product in a state where only we can maintain it.
Have a project to build?
Tell us what you need and we'll give you an honest technical opinion before talking budget. No commitment.
Book a meeting