Skip to content
DATA FACTORY
ONLINE

Data Factory Online

The software adapts to your process. Not the reverse.

I design and build custom digital tools for small and mid-sized companies. The working version arrives in weeks, I take care of professional hosting with backups, and the source code is yours from day one.

Scroll

3–6

weeks to the first working version

0

monthly per-user licences

100%

of the source code, in your hands

EN · ES

bilingual from the first delivery

01 The starting point

The cost of generic

A large suite covers 60% of your operation and bills you for the forty modules you never opened. The remaining 40% ends up where it always does: in a shared spreadsheet, in a WhatsApp group, and in the head of the person who has been there twelve years.

Generic service
Custom-built tool
You pay every month per user, whether the system is used or not.
You pay once for what was built for you.
Your team bends the process to fit the software.
The software reproduces the process that already works.
A small change means a ticket and a three-week wait.
A small change enters the next phase, within days.
You share infrastructure with thousands of accounts and no visibility into the backups.
I run the hosting on professional servers, with backups and monitoring included.
If you leave, you walk away with an export file.
If we part ways, you walk away with the whole system and I help you migrate it.
02 Five commitments

The pillars of the work

Not brochure values: these are the rules that decide what gets built, what it costs, and what you keep at the end.

01

Exact fit

Nobody configures someone else's product here: yours gets built. Every field, business rule and screen exists because your operation asked for it, not because it came in the template.

02

Proportional cost

No per-user licences and no surprise pricing tiers. A bounded scope, a fixed price per phase, and managed hosting included at an accessible cost.

03

Immediate response

Short, cumulative phases. A change of criteria doesn't open a quarter-long renegotiation: we discuss it today and it lands in the next increment.

04

Full ownership

You receive the source code, the database schema, the installer and the manual. Nothing stays locked behind an account I control.

05

Continuous evolution

The MVP is the starting point, not the finish line. Each phase adds capability without breaking what your team was already using yesterday.

03 How it gets built

Short phases, usable deliveries

The method is the same on every project: cumulative phases, each one closed, verified and running before the next one opens.

Phase 0

Diagnosis

A working session to map the real process: who does what, where it breaks, and which decision is made with which piece of data. It produces a written scope and a fixed price.

Deliverable: kickoff document
Phase 1

Working core

The minimum version that already helps: users, roles, the main flow and the guided installer. It gets installed and used from the very first delivery.

Deliverable: installable system
Phases 2…n

Increments

Each phase adds a closed block verified with smoke tests. Zero regressions: whatever worked in the previous phase keeps working.

Deliverable: numbered release
Handover

Transfer

Code, bilingual manual, installer, backups and training for your team. The explicit goal is that you can run it without depending on me.

Deliverable: manual and training
04 Familiar ground

What can be built

Modules I have already built and tested on real platforms. They get combined according to what your process needs; no two projects are alike.

01

Process automation

Flows with states, approvals, owners and deadlines. What currently lives in chains of forwarded email.

02

Client portals

A dedicated login for each client or supplier: their information, their documents, their history.

03

Scheduling and calendars

Rule-based availability, bookings, buffers and two-way synchronisation with Google Calendar.

04

Dashboards and metrics

The numbers that actually get reviewed every week, calculated from the source instead of by hand.

05

Document management

Upload, versioning and in-browser viewers for PDF, Excel, Word, slide decks and notebooks.

06

Roles, permissions and audit log

Each user sees only what belongs to them, and there is a record of who changed what and when.

07

Email and notifications

Transactional alerts, reminders and password recovery sent from your own domain.

08

Data import

Migrating what lives in spreadsheets today, with validation and a report of whatever doesn't add up.

09

Integrations

Connections to the tools you already use, always optional: if the third party fails, your operation carries on.

05 What you receive

Nothing stays on my side

Every closed version ships as a complete package. That is the difference between hiring a service and acquiring an asset.

01Complete source code, with no obfuscated parts or locked modules

02Guided installer that writes the configuration and applies the migrations

03Bilingual interface in Spanish and English from the first delivery

04Operations manual and a training session with your team

05Numbered, packaged releases so you can always roll back

06Managed hosting with backups, on a standard stack you can migrate away

06 Early honesty

Who this works for

Good fit

  • Companies of 5 to 200 people with a clear, repeatable process.
  • Anyone already paying for three subscriptions that don't talk to each other.
  • Anyone running a critical operation out of a shared spreadsheet.
  • Anyone who needs an internal tool and can't find one that fits.

Poor fit

  • Anyone who needs an off-the-shelf product running this afternoon.
  • Anyone who requires formal compliance certifications from day one.
  • Anyone still unsure which process to solve: that starts with the diagnosis.
  • Anyone choosing on lowest price rather than fit to the process.
07 Before you write

Frequent questions

What does it cost?

A fixed price per phase, with no per-user charge. The range depends on the scope that comes out of Phase 0, and that diagnosis is quoted separately so you can keep it even if you decide to build with someone else.

How long does it take?

Phase 1 — the core that already gets used — usually takes three to six weeks depending on the complexity of the main flow. Later phases ship on shorter cycles.

Where does the software live, and who maintains it?

I take care of the hosting: professional servers, security certificate, automatic backups and monitoring, within an accessible monthly fee. That way the service has a single owner and you don't administer infrastructure. And because the stack is standard (PHP and MariaDB), if you ever prefer to move it to your own provider, it migrates without rewriting anything.

What if I need changes after handover?

They open as new phases with fixed scope and price, or under a monthly maintenance agreement if the pace of change justifies it. You can also make them with your own team: you have the code.

What happens if we stop working together?

You keep everything delivered: code, database, installer, manual and a full backup, and I walk you through the migration to whichever provider you choose. I run the hosting while we work together, but the system never stops being yours.

Do you work with companies outside Mexico?

Yes. The work is remote and the deliverables are bilingual; coordination happens over video calls in whatever time slot we agree on.

08 Next step

Tell me which process is costing you money.

Write to me about the part of your operation that hurts and I'll come back with a first read: whether it's worth building something, roughly how big it would be, and where I'd start. No cost, no commitment.

Your details are used only to answer this enquiry. They are not shared with third parties or added to mailing lists.

Get in touch