Start with an audit

Let’s talk.

Tell us what you’re working on. A person from the team replies to every enquiry, with a time for a 30-minute call.

What do you need?
Your details are sent over a secure, encrypted connection and only used to reply to you.
Specialist service · custom web application development

Custom web applications

Build custom when the workflow is your competitive edge, when per-user licence fees will exceed build cost within two to three years, or when low-code limits on logic, integrations or data residency block you.

Product Engineering practice: abstract red and ink artwork from the Red Balloon reel

Off-the-shelf software fits most of a business, and custom web application development is for the part that does not: the approval chain, pricing logic or field process that sets you apart. Red Balloon builds custom web apps for EPC contractors, NGOs, distributors, clinics and service firms that have outgrown spreadsheets or low-code tools. We map how work actually moves, design screens for each role, and build in permissions, audit logs and approval reminders from the start. A first version goes live early and improves on real usage rather than guesses. Custom web application development cost depends on roles, workflows, integrations and offline needs, and you own the code, hosting and data throughout.

What drives custom web application development cost

Custom web application development cost follows the complexity of the workflow more than the number of screens. The main drivers are how many roles the app serves, how many approval paths and exceptions it must handle, and how many systems it connects to, such as Tally, an ERP, an HR tool or a payment gateway. Offline capture for field teams, document generation, and data migration from spreadsheets or a low-code platform each add their own work.

Reporting and audit needs matter too, as do languages and any sector rules on data handling. We scope these during workflow mapping, then quote a fixed first release with a list of what is in and out. Hosting and yearly upkeep are estimated at the same time, so you see the full cost before deciding.

Getting staff to actually use the new app

Internal tools fail more often from low adoption than from bugs. People keep using WhatsApp, email and their old spreadsheets because those still work and nobody has told them to stop. We plan the switch with you from the start: a champion in each team who tests early builds, short role-specific training videos, and a clear date after which requests outside the app are no longer accepted.

Rollout usually runs one site or department at a time, so problems surface on a small scale. Usage reports show who has logged in and which tasks still happen elsewhere. Feedback from the first weeks goes straight into small fixes, which shows staff the app is listening to them rather than being imposed on them.

What the second and third releases usually add

Once the core workflow runs in the app, the data it collects becomes useful. Second releases often add dashboards for managers, automatic reminders and escalations, and connections that remove the last manual exports. Our AI & Automation practice can add document reading for invoices or delivery notes, with a person reviewing anything uncertain, or summaries that save managers from reading every record.

Third releases tend to open the app to outsiders, such as vendors submitting bills or customers tracking requests, which is where our portals work begins. Each release is planned from usage data and feedback rather than the original wishlist, and judged on the primary metric agreed at the start, such as approval time or same-day closure.

Where this works

Real-world situations we're built for

Illustrative · not a client
Construction / EPC

Noida EPC contractor approves purchase requests over email and WhatsApp with no audit trail

What we'd do
Custom web app with multi-level approvals, budget checks against project codes, PDF purchase orders and an audit log
What moves
Goal: approval cycle time down, off-budget purchases down, measured as approval cycle time before and after, over a fixed period
NGO / social sector

Delhi NGO runs paper field surveys across three states; data entry takes weeks

What we'd do
Offline-capable PWA for field staff with Hindi forms, background sync and a donor-report dashboard
What moves
Survey-to-report time down, data entry errors down
How a project runs

3 phases, each with a deliverable

What happens, how long it takes, what you get and what we need from you.

Workflow mapping

1–2 weeks

Roles, permissions, approvals, exceptions, data volumes, build-vs-buy comparison

You get: Role matrix and workflow specification

We need: Process owners from each team

Build

6–14 weeks

APIs, UI, access-control tests, audit trail, integrations

You get: Staging app every sprint

We need: Test users and sample data

Migration and launch

2–3 weeks

Data migration, parallel run, user training

You get: Live app and admin guide

We need: Sign-off on migrated data

A typical engagement

From first call to result

Illustrative · not a client

Gurugram facilities-management company, 1,500 field technicians, Zoho Creator app hitting its limits

Weeks 1–2Build-vs-buy reviewCompare platform limits and three-year licence cost with a custom build; map roles and approvalsDecision to build custom with phased migration
Weeks 2–4Roles and workflowsRole-permission matrix, approval state machine, offline rules for technicians; check first who approves when the usual approver is on leaveSigned-off workflow specification
Weeks 4–12BuildReact PWA with IndexedDB offline queue, Node.js API, PostgreSQL, audit log, SSO for office staffStaging app loaded with pilot data
Weeks 12–15Migrate and switch overExport old records, migrate in batches with row counts and checksums, run both systems in parallel at one site for two weeksOld platform retired
Where it starts9,000 work orders/month, slow pages, rising per-user licence costs, no offline mode for basements and plant rooms
Where it endsA custom work-order app with offline mode and approvals. Weekly watch: work orders closed the same day, sync failure rate, approval turnaround time.
What we measure

The numbers we report on

Every metric has a formula, a target, a source and a reporting rhythm.

MetricHow it's calculatedTargetSourceCadence
Workflow cycle timeMedian time from request created to final approvalSet from your current baseline, then aim for 30% fasterApp database reports in MetabaseWeekly
Permission test pass rateAutomated permission tests passing ÷ total permission tests100% before every releaseCI test reportsEvery release
Offline sync failure rateQueued records failing to sync ÷ records queuedRule of thumb: under 0.5% of queued records failing; any record still unsynced after 24 hours raises an alertSentry and application logsWeekly
Active users by roleWeekly active users ÷ invited users, per roleSet from rollout baseline; low roles reveal adoption gapsPostHog or GA4 with user propertiesWeekly
Automated by default

What runs itself after launch

The manual work we take out of this service, and the tools we use.

When: Approval pending past its SLAApproval reminders and escalationsScheduled jobs in the app or n8n sending email and WhatsApp remindersRemoves: Requests stuck with one approver
When: Every pull requestPermission regression testsAutomated API tests per role with Jest or Playwright in CI, one test for each cell of the role-permission matrixRemoves: A change accidentally exposing data to the wrong role
When: DailyAudit log exportNightly job to Amazon S3 or Google Cloud Storage with retention rulesRemoves: Losing evidence needed for audits and disputes
Rules we work to

Standards and regulations

OWASPOWASP ASVS (access control requirements)

Enforce permissions server-side on every request; broken access control tops the OWASP Top 10 2021

MeitYDPDP Act 2023 and DPDP Rules 2025

Collect only the employee and customer data you need, set retention periods and log access to personal data; main duties apply from 13 May 2027

W3CWCAG 2.2

Internal tools are used all day; accessible forms and keyboard support help every user

What's changing

Platform and policy updates that affect this work

We track: OWASP Cheat Sheet Series, React blog.

React (Meta)React 19 stable added Actions and improved form handling

Form-heavy internal apps get simpler patterns for saving data

Vercel (Next.js)Middleware authorisation bypass CVE-2025-29927 disclosed and patched

Access checks must live in server code, not only in middleware

Before you hire anyone

Questions to ask any agency, including us

How will you model permissions so we can change roles later without code changes?

Why ask

Org charts change; hard-coded roles become expensive

A good answer

A role-permission data model with admin screens and automated tests per role

How will you migrate data from our spreadsheets or current tool?

Why ask

A bad migration breaks trust on day one

A good answer

Field mapping, cleaning rules, trial migrations and a sign-off step

What will the app cost to run and maintain each year?

Why ask

Custom apps carry ongoing hosting and upkeep costs

A good answer

An itemised hosting estimate and a maintenance plan with a clearly stated retainer

FAQ

Questions buyers ask us

Straight answers from the practice lead. Highlighted text marks Red Balloon figures we confirm before publishing.

How do you build role-based access and approval workflows into a custom web app?

Permissions are modelled as roles plus attribute rules, such as region or amount limits, enforced on the server for every request, with multi-step approvals and an append-only audit log of who changed what.

  • Libraries such as CASL or Casbin keep permission rules in one place instead of scattered across screens.
  • Maker-checker flows, where one person creates and another approves, suit finance, lending and procurement teams.
  • Audit logs are retained per your policy, commonly at least 180 days to align with CERT-In log rules.
  • We write permission tests per role and call the API directly as each role; a hidden button is not a permission check.
Can a custom web app work offline for field teams on patchy networks?

Yes, when built as a progressive web app with a service worker and IndexedDB: it can capture forms, photos and orders offline and sync them when the connection returns.

  • Sync needs a conflict rule, such as last-write-wins or server-side review, decided per data type before build; retrofitting one later is the expensive part.
  • The Background Sync API works in Chrome on Android but not Safari, so iOS users sync when they reopen the app. Compress photos on the device to save mobile data.
Can a custom web app read invoices, forms or documents automatically?

Yes. We combine OCR with a language model to pull fields such as vendor, amount, GSTIN and dates from scanned or photographed documents, then validate them against your records. Anything below a confidence threshold goes to a person to check, and every correction improves the rules. Document reading usually arrives as a second-release feature, once the core workflow is stable.

  • OCR plus a language model
  • Low-confidence items checked by a person
  • Usually a second-release feature
How is custom web application development in India kept secure after launch?

Through routine work rather than a one-off test. Dependencies are updated on a schedule and scanned for known vulnerabilities in CI, permission tests run on every release, access is reviewed when staff change roles, and backups are restored as a test. Before go-live and after major changes, an independent penetration test checks what automated tools miss.

  • Scheduled dependency updates
  • Permission tests every release
  • Penetration tests at key points
Back to the service

Web app development →

Start with an audit

Ready for
lift?

A paid two-week Growth Audit covers your funnel, ads, site, tracking and automation gaps, and ends with a 90-day plan you can run with or without us. The fee is credited against your next engagement.

Prefer to talk? Call +91 97114 48083, or email info@redballoon.in.

A person from the team replies to every enquiry.

What do you need?
Your details are sent over a secure, encrypted connection and only used to reply to you.