GBCORP BLOG · IT SERVICES
SaaS Web Application Development: The Browser Is the Product
Most business software is used in a browser, at a desk, for hours. A SaaS web application has to be fast, clear and reliable there first, and the phone app comes second.
SaaS web application development produces a product businesses use in a browser and pay for monthly: each customer with its own data and users, plans and billing that renew, and an operator console watching the whole base. GBCORP builds SaaS web applications on the multi-tenant core that runs its own products, so tenancy, billing, sign-in and the console are in place in week one and the work goes into the feature customers pay for, delivered in fixed-price releases with the code and the accounts in the founder’s name.
What comes from the core
| Part | What it covers | Source |
|---|---|---|
| Tenancy | Data, users, roles and branding per customer, isolated at the database | Core |
| Billing | Trials, plans, renewals, upgrades, invoices, to the operator’s own gateway | Core |
| Sign-in | E-mail, single sign-on for enterprise customers, two-factor for administrators | Core |
| Console | Tenants, revenue, churn, feature use, support | Core |
| The product | The feature customers pay for, in the browser first | Built per product |
| API | Documented endpoints per tenant with keys and limits | Core, exposed per product |
The browser first
A web application used for hours must load instantly, keep state when the connection blinks, work with the keyboard, print properly, and be accessible. Tables that handle thousands of rows, filters that remember, exports that run in the background. GBCORP designs the web application at real desktop sizes first and adds the phone app from the same codebase when customers need it.
Security questionnaires, answered from the design
Enterprise customers ask before they buy: where is the data, who can see it, is it encrypted, is there an audit log, can we export, is there single sign-on. The core answers each from its design: isolation enforced at the database, encryption in transit and at rest, audit logs per action, export per tenant, single sign-on as a plan feature. A founder with these answers closes larger customers.
Metrics from the first paying month
Trials started and converted, recurring revenue and churn by plan, active tenants and the features they use, support tickets by feature, time to first value per cohort. All in the operator console, so the roadmap is decided from evidence rather than from the loudest customer.
Checklist before building a SaaS web application
- The one job the product does for a paying customer.
- The first plan and its price.
- Ten customers who will trial it.
- Markets, currencies and tax rules.
- Payment-gateway account in the founder’s name.
- The number that defines success at three months.
The numbers to expect
Scoping in one week. A first paying release in eight to twelve weeks at a fixed price, with tenancy, billing and console from the core. Releases every two weeks. Support at a known monthly figure. Customised or more complex functionality is quoted separately before any work starts.
A worked example
A compliance consultancy has a method its clients pay for in workshops and wants to sell it as software. On the multi-tenant core, tenancy, billing and the console exist in week one; weeks two to ten build the method as a guided web application with evidence uploads, reviews and a report. Ten clients trial it in week eleven; six subscribe. An enterprise prospect sends a security questionnaire, and every answer comes from the design. Single sign-on is switched on for that customer as a plan feature. The founders read time to first value per trial and change the onboarding in release two.
Roles, permissions and audit inside a tenant
A business customer has administrators, editors and viewers, sometimes by department. The core provides roles per tenant, permissions per feature and an audit log per action that the tenant’s administrator can read and export. These are the questions an enterprise buyer asks in the second call, and the product answers them from the first release.
The API and integrations later
Customers ask for an API and integrations with the tools they already use within the first year. The core exposes a documented API per tenant with keys and rate limits, and integrations are built as releases in the order customers ask for them. The first release does not include them, on purpose: the console shows which integrations matter, and the founders build those.
Support inside the product
A help panel with the articles that answer common questions. A message thread per tenant that reaches the operator console. Status shown in the app when something is wrong. Tickets by feature in the console, which is the list of what to fix or explain next.
Multi-market from the first release
Currency, tax and payment provider per market, with right-to-left layouts as a setting, are in the core. Tenants belong to a market; the console reports per market and combined. The second language is a release when customers ask for it.
Ownership terms
Code in a repository the founder controls, documented with every release. Cloud project, domain, gateway and store accounts in the founder’s name. Tenant data exportable per tenant. No equity, no revenue share, and no credentials retained after a hand-over unless a support contract requires them.
Questions we hear first
Web only, or app too?
Web first; the phone app comes from the same codebase as a later release when customers ask for it.
Can customers white-label our product?
Yes. Per-tenant branding and a custom domain per tenant are part of the core.
Who owns the product?
The founder: code, cloud project, gateway and store accounts in its name; no equity, no revenue share.
Can enterprise customers get a dedicated deployment?
Yes, from the same code, as a plan feature.
Where to start
The GBCORP Custom App Development product is the priced starting point; the GBCORP web development hub sets out the approach. For the business model side, read SaaS software development explained.
GBCORP operates across 17 countries on 4 continents through six pillars: AI & IT, Innovation, Sustainability, Infrastructure, Premium Business, and EV's & Solutions.
