GBCORP BLOG · IT SERVICES
SaaS Software Development: Building a Product Customers Subscribe To
A SaaS product is software that signs up its own customers, bills them every month and keeps them without a salesperson in the room. The development has to serve that business model, not only the feature list.
SaaS software development produces a product many businesses subscribe to: each tenant with its own data and settings, plans with limits and prices, billing that renews itself, onboarding that needs no call, and a console from which the operator watches the whole customer base. GBCORP builds SaaS products on the same multi-tenant core that runs its own white-label range, so the tenancy, billing and console parts are proven before the product’s own features are written, and the first paying release ships in weeks at a fixed price.
The parts every SaaS product needs
| Part | What it does | Built or reused |
|---|---|---|
| Tenancy | Each customer’s data, users, settings and branding isolated | Core |
| Plans and limits | Free, starter, pro; seats, usage, features per plan | Core |
| Billing | Trials, renewals, upgrades, failed payments, invoices, to your own gateway | Core |
| Onboarding | Sign-up, first-run setup, sample data, in-app guidance | Per product |
| Operator console | Tenants, revenue, churn, support, feature flags | Core |
| The product itself | The feature customers pay for | Per product |
Billing that runs without a person
Trials that convert or expire on a date. Renewals charged to the customer’s card through the operator’s own payment gateway. Upgrades prorated, downgrades applied at the period end, failed payments retried and then restricted with notice. Invoices issued with the operator’s tax details per market. The finance report reconciles to the gateway to the cent, which is what makes the revenue figure believable.
Onboarding is a feature
The first five minutes decide whether a trial converts. Sign-up with a work e-mail, a setup screen that asks three questions, sample data so the product is not empty, and a checklist of the actions that predict retention. GBCORP measures time to first value per cohort, because it is the number that moves conversion most.
The metrics that decide the roadmap
Trials started and converted. Monthly recurring revenue and churn by plan. Active tenants and the features they use. Support tickets by feature. These sit in the operator console from the first release, so the roadmap is decided from evidence rather than from the loudest customer.
Checklist before building a SaaS product
- The one job the product does for a paying customer.
- Plans with prices and limits.
- Markets, currencies and tax rules.
- Payment-gateway account in the operator’s name.
- The first ten customers and how they will hear of it.
- 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 consultancy has a spreadsheet method its clients pay to use, and wants to sell it as software by subscription. On the multi-tenant core, tenancy, plans, billing and the console are in place in week one. Weeks two to ten build the method itself as a guided workflow with reports. The first ten customers trial it in week eleven; four convert. The console shows which step of onboarding the six others abandoned, and release two fixes that step. Monthly recurring revenue is a number on a screen from the first paying month, reconciled to the gateway.
Security and isolation between tenants
Each tenant’s data is separated by rules enforced at the database, not only in the application, so a bug in a screen cannot show one customer another’s records. Roles per tenant, audit logs per action, two-factor sign-in for administrators, and exports per tenant on request. A security questionnaire from an enterprise customer is answered from the design rather than from promises.
Pricing the product itself
Plans are configurations: seats, usage limits and features per plan, changed in the console without a release. Annual plans with a discount, a free tier with limits, and add-ons priced separately. Grandfathering an old price for existing customers is a setting. GBCORP builds pricing as data because founders change it often in the first year, and each change should take minutes.
Support inside the product
A help panel with the articles that answer the common questions. A message thread per tenant that reaches the operator console. Status shown in the app when something is wrong. Support tickets by feature in the console, which is the list of what to fix or explain next. Founders read this list weekly; it is cheaper than a survey.
Growth built in
Referral links per tenant with rewards. Trials that start from a shared link. Usage nudges when a tenant approaches a plan limit, offering the upgrade in the app. Annual plan offers at renewal. These are configurations of the core, switched on when the founder wants them, and each shows its result in the console.
Ownership of the product
Code in a repository the operator controls, documented with every release. Cloud project, domain, gateway and store accounts in the operator’s name. Tenant data exportable per tenant. No revenue share with GBCORP, and no credentials retained after a hand-over unless a support contract requires them.
Questions we hear first
Multi-tenant or one deployment per customer?
Multi-tenant by default; a dedicated deployment for a customer that requires it, from the same code.
Can customers white-label our SaaS?
Yes. Per-tenant branding and a custom domain per tenant are part of the core.
Who owns the product?
The operator: code, cloud project, gateway and store accounts in its name.
Can we add AI features later?
Yes. A model step is added as a release, with a review screen and measurement.
Where to start
The GBCORP software development hub sets out the method; the GBCORP Custom App Development product is the priced starting point. For the service view, read SaaS development services explained.
GBCORP operates across 17 countries on 4 continents through six pillars: AI & IT, Innovation, Sustainability, Infrastructure, Premium Business, and EV's & Solutions.
