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.
Data Factory Online
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
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.
Not brochure values: these are the rules that decide what gets built, what it costs, and what you keep at the end.
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.
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.
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.
You receive the source code, the database schema, the installer and the manual. Nothing stays locked behind an account I control.
The MVP is the starting point, not the finish line. Each phase adds capability without breaking what your team was already using yesterday.
The method is the same on every project: cumulative phases, each one closed, verified and running before the next one opens.
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 documentThe 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 systemEach phase adds a closed block verified with smoke tests. Zero regressions: whatever worked in the previous phase keeps working.
Deliverable: numbered releaseCode, 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 trainingModules I have already built and tested on real platforms. They get combined according to what your process needs; no two projects are alike.
Flows with states, approvals, owners and deadlines. What currently lives in chains of forwarded email.
A dedicated login for each client or supplier: their information, their documents, their history.
Rule-based availability, bookings, buffers and two-way synchronisation with Google Calendar.
The numbers that actually get reviewed every week, calculated from the source instead of by hand.
Upload, versioning and in-browser viewers for PDF, Excel, Word, slide decks and notebooks.
Each user sees only what belongs to them, and there is a record of who changed what and when.
Transactional alerts, reminders and password recovery sent from your own domain.
Migrating what lives in spreadsheets today, with validation and a report of whatever doesn't add up.
Connections to the tools you already use, always optional: if the third party fails, your operation carries on.
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
Good fit
Poor fit
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.
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.
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.
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.
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.
Yes. The work is remote and the deliverables are bilingual; coordination happens over video calls in whatever time slot we agree on.
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.
Another channel
WhatsApp Coming soon
In the meantime, the form and email are the direct route: admin@datafactoryonline.website