Technology · Strategy · Results

Bespoke software does not grow on its own: it is built.

I digitalise processes for small and medium businesses. Piece by piece, with judgement, until the business runs better than it did.

What I do

Four versions of the same thing: look at how you work, and build what is missing.

  • 01Bespoke development
  • 02Automation
  • 03Applied AI
  • 04Consulting

Bespoke development

Your business is not like the others. Your software should not be either.

Off-the-shelf tools make you work their way: half of what you pay for is surplus, and the part you actually need is missing. I build the piece that fits your process, not the other way round.

Generic tools do not fail for being small. They fail for being another shape.

Drag to compare the two screens
ClientSilvia L.
Cost centre
Item code
Department
ServiceOther

12 fields. Three are of any use. And what you need is not there.

An illustration, not a client screenshot.

Automation

What you do a hundred times a month, you should do once.

Quotes, reminders, sign-ups, reports. Repetitive work does not go away on its own: you define it once, with judgement, and from then on it happens without anyone pushing it.

The first one you define yourself. The rest, you do not.

Put your own numbers in

Per year, by hand

138hours

Automated, it gives back

127hours

The sum, in the open: minutes × times per week × 46 working weeks. 8 % is left for supervision, because automating does not make the work vanish: it stops a person having to do it.

Applied AI

AI that decides on your data, and tells you why.

It takes no magic for a system to settle the routine cases and leave you only the ones that need judgement. What it does take is being able to open it up and see what it decided, and under which rule.

It settles the routine on its own. The rest it hands to you, with the reason.

One booking request. Change the conditions.

Confirmed automatically

Returning client, and the diary is free.

Or load an example

Consulting

Before building anything, work out what is surplus.

Most process problems are not fixed by adding tools. They are fixed by looking at them from the right place — and from there, there is almost always less to build than it seemed.

Crossings in view

214

Why a biznaga

Made by day. It opens at night.

A biznaga is assembled by hand, one jasmine at a time, and you cannot really appreciate it until evening falls and the flowers open. Software is the same: nobody sees the work. What people notice is that the business runs better than it did yesterday.

Work

Three projects. One explains the rest.

They are not worth the same and I am not going to pretend otherwise. Kukelure shows what I can build; the other two show where I come from.

Kukelure

Booking platform · full design and development

A beauty clinic in Pizarra that arranged every appointment over WhatsApp, one at a time. Today the client sees the real openings and takes the one that suits her; Silvia opens the panel and accepts or declines.

  • Availability engine with variable opening hours
  • Two roles, with row-level security
  • Transactional email with a private link to the booking

Before this

ProcesosBI

Corporate site and branding

Management-systems consultancy. Biznaga’s first client: identity, copy, and a page that explains a service which is hard to explain.

Visit

Glitch Night

Web development

The website for a Málaga nightlife app, from before the freelance years. I built the website. The product is not mine, and today the app’s owner maintains it.

Visit

Results · Kukelure

What changed, and where every number comes from.

Gone on the busiest day, purely answering messages to arrange appointments.

2 h 05

25 conversations × 5 min

Appointments a week, arranged by hand one at a time.

50

in the busiest week

Messages needed today to make a booking.

0

the client sees the slot and takes it

These are peak figures reported by the person who built the system, not the output of an analytics tool. They are stated as what they are: the busiest day and the busiest week.

Read the full case

How I work

You know what happens at every step, and what is expected of you.

Commissioning bespoke software is daunting when you do not know what to expect. Here is what happens, in order, and what comes out of each step.

  1. 01

    We talk

    Half an hour, by phone or wherever suits you. You tell me what is giving you trouble; I tell you whether software fixes it or not. Sometimes it does not.

    You come away with

    An honest opinion, free and with no strings.

  2. 02

    I look at how you work

    The real processes, not the ones on the org chart. Where time is lost, what gets done twice, and what gets written on a piece of paper nobody can find later.

    You come away with

    A document with what is surplus and what is missing.

  3. 03

    I propose what to build

    Scope, timeline and price fixed in writing, in phases if the job is large. No open-ended hours and no surprises halfway.

    You come away with

    A quote you can compare and turn down.

  4. 04

    I build it

    With partial deliveries you can use from the first week. No disappearing for two months and coming back with something that was not it.

    You come away with

    A working version, and a meeting every fortnight.

  5. 05

    I put it live and stay

    Training for whoever will use it, going live, and a support period. After that, maintenance if you want it — and if you do not, the code is yours all the same.

    You come away with

    Everything working, documented and in your hands.

About me

Juanma Fernández. I do the work and I answer for it.

Biznaga Consulting is a one-person consultancy, and that is an advantage rather than an apology: the person you talk to is the person who writes the code. There is no salesperson promising and a team finding out later.

I work out of Málaga with companies whose processes have outgrown them. Before proposing anything I look at how you actually work, because often enough the problem is not one software can fix — and saying so is part of the job.

My earlier work, my background and my personal contact details live in my portfolio.

View the portfolio

Frequently asked

What people ask before deciding.

What does it cost?

It depends on the scope, which is why you will not find a price list here: it would be made up. What I can commit to is the shape of it — a fixed quote in writing before starting, in phases if the job is large, and no open-ended hours. The first conversation is free.

How long does it take?

A specific automation can be weeks. A platform with users, permissions and transactional email is months. The timeline is in the proposal in writing, and you will see working versions long before final delivery.

Who owns the code?

You do. It is delivered in your repository, documented, with the keys to everything. I do not work with anything that ties you to me: if one day you want to continue with someone else, they can, without starting from scratch.

What if I want to change something halfway?

We talk about it. Small changes go in; anything that moves the scope is quoted separately before it is touched, so nobody discovers the invoice at the end. Working in phases exists precisely for this.

What happens after delivery?

There is a support period included. After that, monthly maintenance if you want it: updates, backups, monitoring and a direct line. If you do not want it, the software is still yours and still working.

I am not in Málaga. Is that a problem?

No. Remote works just as well, and most meetings are video calls. If you are nearby and would rather meet, even better.

Contact

Shall we talk?

Tell me what is giving you trouble. No forms, no promises of a reply within 24 hours: you write, and I answer.