Quick Summary
- What this covers
- The no-code stack that replaces custom apps
- Use cases
- Field ops · HR · Leads · Warehouse · Finance
- Stack
- Fillout · Airtable · Zapier · Google Workspace
- Build time
- 4–6 weeks per system
- Ownership
- 100% client-owned — no vendor lock-in
The Crossroads Every Growing Business Hits
Most growing businesses eventually reach the same crossroads: the spreadsheets and group chats that held things together are no longer cutting it, and someone in the room says "we should build an app for this."
And then the quotes come in. Six figures. Six months. A development team you'll need to maintain indefinitely. A system that's already outdated by the time it launches.
Here's what I tell every client who reaches that crossroads: you don't need to build an app. You need a system that works like one. I've been building exactly that — for field operations, HR, lead management, warehouse tracking, and more — using a no-code/low-code stack that costs a fraction of custom development and deploys in weeks, not months. Where custom scripting is needed, it's built as part of an automated, repeatable system — not one-off spaghetti code.
Why Custom App Development Is Usually the Wrong Answer
Custom apps make sense in a narrow set of circumstances — when you have unique technical requirements no existing tool can meet, when you have the internal resources to maintain the codebase long-term, and when you've already validated exactly what you need to build.
Most growing businesses have none of those things. What they have is an operational problem that's getting more expensive to ignore — and the assumption that solving it requires building something from scratch.
The reality: the vast majority of internal operational tools — field reporting portals, HR onboarding systems, lead capture databases, expense trackers, warehouse request forms — can be built on existing no-code platforms in a fraction of the time and cost. And they'll work better, because they're built on tools your team already understands.
The shift in thinking: stop asking "what app should we build?" and start asking "what problem are we actually trying to solve — and what's the fastest way to solve it properly?"
The Stack
Fillout
branded, mobile-optimized forms and portals with conditional logic, file uploads, multi-step flows, email authentication, and custom domain hosting
Visit Filloutdatabase layer
Airtable
relational database, automation engine, and dashboard platform in one; every submission stored, linked, and queryable
Visit Airtableautomation layer
Zapier
routes data between platforms, triggers notifications, organizes files, syncs records, and handles workflow logic
Visit Zapier
Google Workspace
Drive for organized file storage, Sheets for finance-ready reporting exports
What This Stack Can Actually Build
The same four tools power completely different systems depending on what your business needs. Here's a cross-section of what I've built and what's possible.
Field Operations & Daily Activity Reporting
Field sales teams submit structured daily reports through a mobile-optimized portal — capturing visit details, customer interactions, proof of visit, and Purchase Order uploads. Data flows automatically into a central database, files organize themselves in Google Drive, and management gets real-time dashboards showing nationwide and regional activity without asking anyone for a report.
Who needs this: trading companies, distribution businesses, FMCG field teams, and agricultural companies with regional agents.
HR Onboarding Systems
A single form submission triggers an entire onboarding workflow — employee records created in the HR database, Google Drive folders auto-generated with predefined naming conventions, department heads notified, and an onboarding checklist automatically assigned. No coordinator manually setting up folders or sending reminder emails.
Who needs this: any business hiring more than five people a month, or any HR team spending significant time on manual onboarding coordination.
Lead Capture & Client Pipeline Management
Leads captured from any channel — website forms, ads, events, referrals — flow into a structured Airtable pipeline with source tagging, automatic follow-up reminders, and status tracking. Sales teams get notified instantly when a new lead comes in, and management sees the full pipeline in real time. No heavyweight ERP subscription required.
Who needs this: B2B businesses, property developers, and service businesses managing a moderate volume of inbound leads.
Expense & Receipt Tracking with Approval Workflows
Field staff submit expenses through a structured portal with required receipt uploads. The system evaluates each submission against configurable finance rules — automatically approving low-value items, routing higher-value items to the appropriate manager, and syncing approved expenses to a Finance-only Google Sheet in an accounting-ready format. The entire approval chain is documented and auditable.
Who needs this: any business with a distributed team submitting expenses — especially those preparing for Odoo or similar ERP integration.
Warehouse & Inventory Request Systems
Warehouse staff submit stock requests, inventory movements, or job orders through a structured form. Requests are logged in a central database, routed to the appropriate approver, and tracked from submission to fulfillment. Management sees live request status without calling the warehouse floor, and discrepancies are flagged automatically against defined thresholds.
Who needs this: manufacturing companies, distributors, and retail operations with multiple storage locations.
What Makes It Feel Like an App
The reason these systems get called "app-like" isn't just the technology — it's the experience. Here's what creates that feel:
- Branded identity — your logo, your colors, your domain; the portal looks like it belongs to your company, not a third-party tool
- Role-based access — different users see different forms, data, and dashboards; Finance doesn't see HR data, field agents don't see management reports
- Conditional logic — forms adapt based on what the user selects, so each role only sees the fields that apply to them
- Automated notifications — confirmations to users, alerts to managers, approval messages to approvers, all without anyone sending them manually
- Real-time dashboards — live nationwide views, regional drill-downs, and individual performance without compiling a single manual report
How Long Does It Take — And What Does It Cost?
Build time depends on complexity, but most systems follow this pattern:
The most important thing: everything is owned by you. Every workflow, database, and automation lives in your accounts. If you ever want to take it in-house or hand it to another developer, you can — no dependency on me to keep your operations running.
One System at a Time — Or All at Once
One of the biggest advantages of this approach is modularity. Each system is built as an independent module — its own forms, its own database tables, its own automation logic. But they share the same infrastructure: the same Airtable base, the same Zapier account, the same branded portal.
That means you can start with the most urgent problem — say, field reporting — prove it works, and then add expense tracking, workplan submission, and HR onboarding on the same platform without rebuilding anything from scratch. The infrastructure scales with you. That's the point.
Platform costs vary with transaction volume and team size — Zapier scales with monthly tasks, Airtable with seats and rows, Fillout with submission volume. Most SMEs starting out should budget roughly ₱10,000–20,000 per month for the full stack, paid directly to the vendors.
The smarter approach: build one system well. Prove the value. Then expand — knowing every new module connects to what you've already built. No integration headaches, no platform migration, just a system that grows with your business.
Running on manual workarounds?
One discovery call and you'll know what's worth automating in your operation, what isn't, and what a working system would look like.