Web & mobile development — Cotonou

Applications delivered on the date we commit to.

A senior team, a stack we know inside out, and a scope written down in full before the first line of code.

Estimate my project Get in touch

Written scope → design → staging → launch

What we build with

Web: React · Next.js · Vue
Mobile: React Native · Flutter
Back end: Node · NestJS · Laravel
Delivery: Docker · CI/CD · Git

What sets us apart

Three commitments, not three slogans.

Deadlines

The date is set before we start.

The scope is written down, split into milestones and costed in days before the first line of code. You know what ships, and when. If something slips, you hear about it the day we do — not on delivery day.

Web & mobile

Both platforms, the same team.

Neither the mobile app nor the back end gets subcontracted. A product that lives on the web and in an app store is designed as one thing: one API, one set of business rules, two interfaces.

Seniority

Six years in the field, not a training ground.

Your project is nobody's opportunity to learn a framework. Architecture decisions are made by the people who will maintain them, and code is reviewed before it is merged.

Expertise

What we build.

Two distinct crafts on one technical foundation. Whether you need web, mobile or both is decided during scoping, based on your users — not on a preferred tool.

Web

Websites and web applications

Marketing and content sites: Built for speed and search, not just to match the mockup. Content you can edit without calling us.
Online stores: Catalogue, checkout, order management and dashboard. Local and international payment methods alike.
Business tools and SaaS: Accounts and roles, admin panels, billing, connections to the tools you already use. What replaces a spreadsheet that outgrew itself.

React · Next.js · Vue

Mobile

iOS and Android applications

Consumer applications: Shipped to the App Store and Google Play, from user accounts to notifications. We handle submission and updates.
Field applications: Built for real conditions: offline mode, scanning, location, syncing the moment the network returns.
Mobile companion to a web product: The same back end, an interface rethought for thumbs. Not a web page wrapped in an app.

React Native · Flutter

Shared foundation

Back end: Node (Express, NestJS), Laravel, PHP, REST APIs
Operations: Docker, continuous integration and deployment, Git
Quality: Code review before merge, a dedicated staging environment, a Git repository that belongs to you

How we work

Four milestones, each with a date.

We don't bill hours into the void. The project is split into milestones whose dates are set during scoping and written into the quote. That is what makes a deadline verifiable rather than promised.

01
Scoping
We start from your problem, not from a feature list. What is out of scope is written down as plainly as what is in it — which is what prevents the awkward conversation halfway through.
What you get
A written scope, split into dated milestones, and a fixed quote.
02
Design
You see the screens before they are built. Feedback at this stage costs an hour; the same feedback after development costs ten.
What you get
The key screens, clickable, for you to approve before development starts.
03
Development
You follow progress rather than wait for it. Every finished milestone is deployed to a staging environment you can click through yourself, without booking a demo.
What you get
A staging link kept up to date, and a progress review at every milestone.
04
Launch
The product goes live and you keep the keys. Nothing stays on our accounts: not the repository, not the hosting, not the third-party access.
What you get
The production release, the Git repository, all access, and deployment documentation.

Technical rigour

What holds the project up.

These practices are not billable extras: they are what makes a date achievable and a product that someone else could pick up.

Code review

Nothing ships without a second pair of eyes

Every change is reviewed before it is merged. It is the cheapest place to find a defect: before it reaches your users.

Staging

An environment identical to production

You test on a faithful copy, with your test data. Surprises surface there, not on launch day.

Deployment

Releases are automated

Deployment is a script, not a ritual. It runs the same way every time, which makes it predictable and reversible.

Environments

The same environment everywhere

Docker removes "it works on my machine". Your project runs identically on our machines, in staging and in production.

Tests

Automated where it matters

We test what is expensive to break: payments, authentication, business rules. No chasing a coverage percentage.

Handover

A project another team could take over

A documented Git repository, environment variables listed, the deployment procedure written down. Not being locked to your supplier is a right, not a favour.

Estimate

Estimate your project in two minutes.

A few questions about what you want to build, and you leave with an estimated timeline and a budget range. No sign-up, no commitment.

Step 1 / …

Where does your project need to live?

This is the only question that changes the rest of the form.

Frequently asked questions

The questions clients actually ask.

Budget, timelines, code ownership, what happens after delivery. If yours isn't here, just write to us.

How much does a project cost?

It depends on the scope, and nobody can answer honestly without knowing it. The calculator gives you a ballpark in two minutes; the firm quote comes after scoping, once what we are building is written down. We bill a fixed price per milestone, not by the hour: you know what you are paying before we start.

What happens if a deadline slips?

You hear about it the day we do, not on the delivery date. A slip almost always comes from a scope that moved or an approval waiting on your side; either way the call is yours: move the date, or take something out of the milestone. What does not happen is finding out at the end.

Who owns the code?

You do, from day one. The Git repository is in your name, with the full history, and you keep access whatever happens. Same for hosting and third-party accounts: nothing stays on ours. You must be able to hand the project to another team without asking our permission.

Do you work remotely?

Yes, and it is how we normally operate, including for clients outside Benin. In practice: a progress review at every milestone, a staging environment available at all times, and a reply within one business day. We adjust to your time zone for meetings.

What happens after launch?

Two options. Either you take over: you have the code, the deployment documentation and the access. Or you keep us on a monthly arrangement — security updates, fixes, monitoring and small improvements. It is quoted separately from the project and can be cancelled: it is not a way of holding on to you.

Can you take over a project already under way?

Often, yes. We start with a short audit of the existing code, after which we tell you plainly what is worth keeping and what would cost more to rescue than to rebuild. The audit is billed, and deducted if you go ahead with us.