Your Excel becomes
a real web app.
That spreadsheet your team has been hacking around for years (quotes, stock, time tracking, dashboards) becomes a proper multi-user web app. Roles, mobile, dashboards, audit log. You keep the data, gain the structure.
- Multi-user with proper roles
- Works perfectly on mobile from day one
- Excel import and export always available
This very site:
If your site were ours, this is how it would score. We hold every migration to the same bar.
Check on PageSpeed Insights →Why your Excel is past its limit.
Three people, three versions
María opens the file, edits, saves. Pedro opens an older copy, edits the same row, saves. Now there are two truths. By Friday there are five.
Formulas nobody understands
The pricing logic lives in a 200-character VLOOKUP that only the founder remembers writing. They are on holiday. Sales gives wrong quotes for a week.
No mobile, no remote, no nothing
Field team has no access. They WhatsApp the orders to the office. Office types them in. Half get retyped wrong. The other half never make it.
Crash, lose work, repeat
The file is 18 MB. Excel hangs. Somebody force-quits. Last 40 minutes of work gone. The team has learned to save every 60 seconds out of pure trauma.
What we build and what we don't.
Internal apps for your team are a fit. Public SaaS launches, real-time trading and regulated banking are not. The line is whether the project fits a small focused team or needs a multi-team operation.
What we migrate
These cases we deliver with confidence.
- Quote / proposal management workflows
- Internal CRM / lead tracking (under 50k records)
- Stock / inventory with simple suppliers + clients
- Time tracking / hours logging / project hours
- Internal dashboards aggregating multiple data sources
- Booking / reservation systems (gym, dental, salon)
- Custom invoicing if Holded does not fit your case
- Lightweight HR (vacations, sick days, holidays)
What we do not migrate
These need a larger team. We recommend looking elsewhere.
- Apps for selling to the public (B2C SaaS launches need product strategy)
- Real-time apps with sub-100ms latency (trading, gaming)
- Apps requiring offline-first sync at scale (use a specialized platform)
- Banking, payments processing or PSD2 regulatory scope
- Multi-tenant SaaS with thousands of customer accounts
- Apps requiring ISO 27001 / SOC2 certification day one
- Anything where the company has not actually run the process manually first
Three scope levels,
picked by complexity.
Three orientative tiers to place your project. Most clients land in STANDARD; SIMPLE is for one focused process, COMPLEX is for full internal suites. Price is set after the free audit.
SIMPLE
BEST FOR: One process, single roleOne process moved out of Excel. Up to 3 views, basic auth, single role.
- 1 process digitized (quotes, stock, time tracking, etc.)
- Up to 3 main views (list, detail, form)
- Basic email/password auth
- Single user role
- Mobile-friendly responsive UI
- Excel import/export from day one
- 30 days post-launch support
STANDARD
BEST FOR: Multi-process, multi-role team3-5 connected processes. Multi-user with roles. Dashboards for the team.
- 3-5 connected processes
- Multi-user with role-based permissions
- Custom dashboards per role
- Email notifications and reminders
- PDF generation (invoices, reports)
- Excel + CSV import/export everywhere
- Audit log of changes
- 60 days post-launch support
COMPLEX
BEST FOR: Internal suite with integrationsInternal suite. Multiple modules, external integrations, advanced dashboards.
- Multi-module internal suite
- API integrations (Holded, Stripe, Mailchimp, etc.)
- Advanced dashboards with custom filters
- Scheduled jobs (nightly imports, reports)
- Webhooks in and out
- Granular permissions (5+ roles)
- Offline-first mobile-friendly UI
- 90 days post-launch support
From your spreadsheet
to your team's new tool.
The hardest part is mapping the unwritten rules. The build is the easy part once we know what the app should do.
Map the current Excel
30-min call walking through your spreadsheets. Which rows mean what. Which formulas hide logic. What people copy-paste from where. Free, no commitment.
Wireframes + proposal
Clickable wireframes showing the new app. Written scope, tailored proposal, timeline. You approve the look and the logic before code starts.
Build with weekly demos
Weekly demo of a working preview. You touch real data, click real buttons. Course-correct early, not at week 6.
Migration + training
Import your existing Excel as the seed dataset. Train your team on the new flow. 30-90 days of support to catch what surfaces in real use.
Real questions,
honest answers.
What technology will you build it on?
+
Astro + React for the front, Supabase or Cloudflare D1 for the database, and either Vercel or Cloudflare Pages for hosting. The stack is modern, fast, well-documented, and the running cost stays low at small scale. You get the full repo at the end.
What's the difference between this and Airtable / Notion?
+
Airtable and Notion are great until they are not. They get expensive fast as you scale, they cannot be deeply customized, and they cannot run logic the way a real app can. Custom is better when: you need specific business rules, you want predictable cost at scale, or you outgrew the spreadsheet metaphor.
Can my team keep using Excel during the transition?
+
Yes. Every tier includes Excel import/export. You can keep the team on Excel while the app gets built, then cut over when ready. Some clients run both in parallel for a month and switch only when the app is proven.
What if I don't know exactly what I want?
+
Then start with the free 30-min call. Half the work is figuring out what the app should be. The mapping process in Step 01 + the wireframes in Step 02 are where the unknowns get answered. Most clients have a clearer picture by the end of week 2 than they did at the start.
Do I get the code?
+
Yes. Git repo in your account, deployable to your hosting. If you ever change providers, any team can pick it up. No vendor lock-in by default.
What about backups and security?
+
Database backups are automated daily (Supabase / D1 do this natively, 7-30 days of retention). Authentication uses industry-standard libraries (auth.js, lucia, or Supabase Auth). HTTPS by default. RGPD-compliant where the data scope requires it.
Can the app run on phones?
+
Yes. Everything is built mobile-first. Your team can use the app from a phone with the same data they use from a laptop. If you need an installable mobile app (iOS/Android native), that is a separate engagement, not this service.
What if I want to add features after launch?
+
After the 30-90 day support window, new features get scoped and quoted separately. Or you take an optional monthly maintenance plan that includes a budget of hours each month for changes. We agree the scope of that plan in the same proposal as the build.
Tell us
your project.
Free 30-min audit, no commitment. We respond within 24 hours with a tailored proposal, or if the project does not fit, an honest recommendation.