Skip to content
Sanfeliu Software

Guides

What is a software factory: how it works on the inside

A software factory is a team that builds custom software with a process that repeats on every project: the same path from start to delivery, proven components that get reused and checks at every step. That is why every project comes out with the same quality and with a price that can be fixed before work starts. The client’s problem goes in, and out comes the software that solves it, up and running and maintained.

Updated

Thirty minutes, free and with no obligation, with the engineer who would lead the project.

The SANFELIU production line: what the client says goes onto the belt, passes through engineering (the terracotta arch), quality, security, AWS and support, and out comes the finished software, where each job is ticked off.

Scroll, or tap a station to see it up close.

1/6 Engineering

Understanding the problem and designing the fix

  • A thirty-minute call with the engineer who will run the project.
  • A prototype with your own data in one to three days, before any price.
  • A fixed price per feature, never by the hour.

2/6 Quality

Every piece checked before it moves on

  • The proposal states in writing what is in and what is not.
  • Short phases, each ending with a real delivery.
  • Bugs in what we built are always fixed.

3/6 Security

Your data and your code, protected

  • The code, the domain and the accounts are in your name.
  • The AI inherits the user’s permissions: it sees nothing they can’t see.
  • AI providers under business contracts that don’t train on your data.

4/6 AWS

Running on AWS

  • Custom software on AWS, with the cloud accounts in your company’s name.
  • Hosting, monitoring and backups, in the continuity pack.
  • We tell you what it costs to run before we start.

5/6 Support

One person, start to finish

  • One point of contact: whoever builds it looks after you.
  • If we can’t help, we tell you on the first call.
  • A monthly pack with no lock-in, fixed per month.

6/6 Software

Your software, live and yours

  • In production and maintained, with the monthly changes it needs.
  • The code is yours: if one day you want another provider, you can.
  • You tell us the problem and out comes the software that solves it.

Custom software, built with a process

What gets made is not the same program for everyone: every project is custom. What repeats is the way it is made. As in a well-organized workshop, every job goes through the same stations, with the same tools and with someone checking the result before it moves on to the next one.

You notice the difference in three things: the price can be fixed because the path is known, deadlines are met because the components have been used before, and the software that comes out can be maintained because everything is built the same way.

How it works on the inside

  1. The problem comes in: what makes you lose hours, who suffers it and what you would like to happen. Nobody talks about technology yet.
  2. It is broken down into pieces: everything the software has to do is a named feature, and each feature has its own price.
  3. It is built from proven components: signing in, permissions, connections to the ERP or to email, alerts. Only what is specific to you is custom-built.
  4. It is tested and delivered in phases: a real delivery every few weeks, which you can use and check.
  5. It goes live and is maintained: hosting, backups, monitoring and changes, so the software keeps working long after it was delivered.

Software factory or developers by the hour

The term has sometimes been used for companies that hire out developers by the hour to other companies. It is not the same thing: there, what you buy is time, and the result depends on who you get and on how you direct the work yourself.

  • What you buy: from a factory, a result that works; with developers by the hour, working time.
  • Who takes the risk: with a factory, the provider, if the price is fixed; by the hour, you do.
  • Who directs the work: in a factory, the process is theirs and you decide what gets built; by the hour, you have to direct it yourself.
  • What you are left with: from a factory, documented and maintained software; by the hour, it depends on who built it.

When a software factory suits you

  • When you have a clear problem and no off-the-shelf program solves it the way you work.
  • When you want to know the price before you start, not an estimate of hours.
  • When you have no in-house technical team that could direct developers.
  • When the software has to be maintained for years, not just delivered.

How we do it at SANFELIU

At SANFELIU, a custom software consultancy in Barcelona, your problem comes in through a thirty-minute call that is free of charge. For one specific tool, you see a prototype with your data within one to three days, before any price; then you get a proposal with a fixed price per feature and a real delivery every few weeks.

We build it on AWS, with the code, the domain and the accounts in your name. Once it is delivered, we maintain it with a monthly plan sized to the solution, with no minimum term. And the person you deal with is the engineer who builds it.

Thirty minutes, free and with no obligation, with the engineer who would lead the project.

Frequently asked questions

What is a software factory?

A team that builds custom software with a process that repeats on every project: the same path from start to delivery, proven components and checks at every step. The software is custom; what is always the same is the way it is made.

Does a software factory mass-produce programs?

No. Every project is custom. What runs in series is the process: how the problem is heard, how it is quoted, how it is built, how it is tested and how it is delivered.

How much does it cost?

It depends on what it has to do, not on the hours. After the call, you see a prototype with your data and get a proposal with a fixed price per feature, which doesn’t change once accepted; for the whole business, the audit ends in a phased roadmap with a fixed price per phase. Reference prices are public on the pricing page.

How long does it take?

Websites and small tools, two to four weeks. Integrations and AI on top of the ERP, in phases, four to twelve weeks. The proposal gives the timeline for each item before work starts.

Tell us about your case in thirty minutes.

Book a meeting with the engineer who would lead the project: thirty minutes, free and with no obligation. If we’re a fit, we tell you how we’d start; if not, who to turn to.

Or email me@joansanfeliu.com

Prefer to write?

Tell us about your case in a few lines and we’ll reply by email.