I turn the daily problems ofsmall businesses into digital tools.
Websites, business tools and custom automation. A process that eats your time, a site that no longer looks like you, a product idea with nobody to build it? Let's talk.
Full-stack developer and partner for small businesses. I build tools, and I stand beside the people using them.
Get to know meComplete products, from first screen to launch: apps, SaaS and sites, with playable mockups to prove it.
See the proof
Modernise, automate, build. In stages, with no three-month tunnel, and you stay self-sufficient at the end.
See the three offersSix rules I don't negotiate, from problem-before-tool to accessibility that isn't optional.
The six rulesA blocker, a project, a simple question: the door is right below.
Get in touchIs one of these sentences yours?
These are the sentences I hear on a first call, in the words of the people saying them. None of them mentions technology. If one of them is yours, you are in the right place, and the rest of this page tells you what to do about it.
Three reasons to call me
Almost everything I ship falls into one of these three. Each starts from a problem you already have, not from a technology I feel like using.
Your site has aged badly. It opens poorly on a phone, it is slow, it talks about you instead of talking to your clients. You avoid handing out the address in meetings, and your prospects find it anyway.
- A fast site, readable on a phone, loading in under a second
- A client-facing message: what you fix, for whom, at what moment
- Search visibility set up at launch, not six months later
- Content you can edit without calling me back
An address you hand out without hesitating, and a visitor who understands in ten seconds what you do for them.
Your business runs on a shared spreadsheet, an inbox and a WhatsApp group. Every quote is retyped, every follow-up depends on someone remembering, and the accurate version is always in one person's head.
- A tool cut to the way you work, not the reverse
- Repetitive steps automated: follow-ups, exports, documents, notifications
- Your current tools wired together rather than replaced for the sake of it
- Hands-on onboarding, so the team actually uses it
The hours nobody bills disappear, and the information sits in one place, current, open to the whole team.
You have a product idea, or a need no off-the-shelf software covers. Nobody can tell you what it costs, how long it takes, or where to start. So the project waits.
- Design phase: specification, scope, each stakeholder's business constraints
- Web and mobile development, shipped in stages on a URL you can open any time
- Integrations and APIs: payments, data, existing tools
- Go-live, a user manual, and code you own
A live product, tested, documented, that you can grow with me or without me.
The rest (client acquisition, retention, team coaching) plugs into these three, once the tool or the site is in place. All services
What it actually looks like
A twelve-person energy-renovation company, from its first call to going live. Eight steps, six weeks, and what gets delivered each time.
- Quotes in a spreadsheet
- The site in three WhatsApp groups
- Grant paperwork filled in by hand
8 steps · 6 weeks
- A quote sent during the visit
- Photos attached to the file, from the site
- Grant paperwork pre-filled
Three problems, three live products.
I build the tools, and I stand beside the people using them.
Amaury Andrade, full-stack developer and partner to small businesses.
I build web and mobile applications: the showcase site that has ten seconds to convince, the line-of-business tool nobody else sells, the automation that gives a team two hours back every day.
But shipping the code has never been enough. I also stand beside the people who use it, because failed projects almost never die of a technical problem.
- Web & mobile applications
- Bespoke business tools
- Automating the repetitive
- Site redesign & design
- Paid ad campaigns
- “Just in case” over-engineering
- Projects where I'd be indispensable
The activity centre
Everything I do, gathered on one board. Four ways in, one destination.
- Web & mobile applications
- Custom SaaS
- Taking over existing code
- Integrations & APIs
What you end up with: a live product, tested, documented, and whose code you own.
See the projectsAnd why now?
Waiting costs, even when it's invisible
Every month with a tool that works against you means prospects forming the wrong idea and hours lost to manual work. That cost shows up on no invoice. That is exactly what makes it dangerous.
Small today, heavy in two years
An automation takes a few days when you think of it early. The same need, piled on three years of patches and workarounds, takes a month, because untangling comes first.
We can start small
Nothing requires launching a full rebuild. One useful first slice, shipped in a few weeks, on a URL you can open: the best way to find out whether we work well together.
What I know how to build.
Full stack, yes. But what I care about is the product: knowing where we're going, fitting it into what already exists, and solving the problems that show up along the way. The stack serves that.
Six rules I don't negotiate.
Non-negotiable rules, learned the hard way. With examples, of course: each one is the mark of a project where I did the opposite.
01The problem before the tool
Design and specification are written and signed off before the first line of code. We know what we're building, for whom, and what stays out.
In practice: the first call never mentions technology, and nothing gets built without a signed-off spec.
02Remove before adding
A feature you removed never breaks. Simplicity isn't a lack of ambition. It's a harder one.
In practice: I often propose cutting things out of scope.
03Ship small, ship often
Development moves in sprints, step by step, each one shipped to a URL you can open. A project that vanishes into a three-month tunnel always comes back slightly wrong.
In practice: a URL from week one, a release at every step.
04Performance is a courtesy
Making someone wait four seconds on a phone is deciding their time matters less than the developer's comfort.
In practice: the performance budget is set before anything is drawn.
05User experience isn't negotiable
Contrast, target sizes, keyboard, reduced motion, and above all a flow that holds up. "The customer is always right" never made a good product: if a choice hurts the experience, I say so, and we find better together.
In practice: I guide you on product and design, not just on code.
06Make people self-sufficient
An indispensable contractor is a risk, not a partner. What I build has to be pickable-up by someone else.
In practice: clear documentation and a hands-on handover.
The problem before the tool
Design and specification are written and signed off before the first line of code. We know what we're building, for whom, and what stays out.
In practice: the first call never mentions technology, and nothing gets built without a signed-off spec.
Remove before adding
A feature you removed never breaks. Simplicity isn't a lack of ambition. It's a harder one.
In practice: I often propose cutting things out of scope.
Ship small, ship often
Development moves in sprints, step by step, each one shipped to a URL you can open. A project that vanishes into a three-month tunnel always comes back slightly wrong.
In practice: a URL from week one, a release at every step.
Performance is a courtesy
Making someone wait four seconds on a phone is deciding their time matters less than the developer's comfort.
In practice: the performance budget is set before anything is drawn.
User experience isn't negotiable
Contrast, target sizes, keyboard, reduced motion, and above all a flow that holds up. "The customer is always right" never made a good product: if a choice hurts the experience, I say so, and we find better together.
In practice: I guide you on product and design, not just on code.
Make people self-sufficient
An indispensable contractor is a risk, not a partner. What I build has to be pickable-up by someone else.
In practice: clear documentation and a hands-on handover.
Let's work together.
A project, a question, an urge to modernise your business?
Write to me. I answer within 24 hours.