TechAppForce

SaaS products

A multi-tenant SaaS product

Sell one product to many customers, and let each one make it their own.

Book a demoSee how it runs
  1. Requested
  2. Confirmed
  3. Checked in
  4. CompletedDone
  5. CancelledSide exit
PassedWaits for a personEvery move is kept in the record's history

The problem

What goes wrong today

Today
Before building the product customers pay for, the team spends months on sign-in, customer accounts, roles, approvals and admin screens. Then every large customer wants its own fields and rules, and the codebase fills with special cases.
Who feels it: SaaS founders, CTOs and product engineering teams

How it runs on TechAppForce

A day with it, step by step

Amber steps wait in a person's work inbox; everything else moves on its own.

  1. Foundations on day oneA small team building scheduling software for physiotherapy clinics starts with records, screens, roles, approvals and notifications already in place.
  2. Their own productEngineers spend the first months on what makes the product different: the booking rules, written as C# record hooks.
  3. A new customer signs upA chain of twelve clinics signs up and gets its own space, with its own users, settings and records.
  4. The customer wants it differentThe chain needs an insurance number on every booking and a manager approval for cancellations. Both are configuration for that customer, not a code branch.
  5. Shipped as a releaseThe change is made in development, checked in QA and promoted as a release with a diff of exactly what changed.
Illustration. The organisation and people are invented.

What gets configured

Settings you can read, change and release

No code for any of this, unless a rule truly needs it.

Records 4

  • Your product’s own entities, such as booking, case or shipment, with their fields0 fields + history, files, comments
  • Customer tenant4 fields + history, files, comments
  • Custom field per customer4 fields + history, files, comments
  • Customer settings3 fields + history, files, comments

Stages 5

  1. Requested
  2. Confirmed
  3. Checked in
  4. Completed
  5. Cancelled

Automatic 4

  • WorkflowEach customer can add fields to a live app without a code change
  • CodeNotifications by email, SMS, webhook and in-app, from templates
  • CodeC# record hooks for the rules that make your product different
  • CodeCustomer sign-up, subscriptions with trials and seats, and recurring billing

Screens and reports 5

  • Your product’s screens, built on the platform’s grids, kanban, scheduler, charts and forms
  • Or a fully branded frontend on the Angular SDK (components) or the React SDK (hooks)
  • Admin screens for each customer to manage its users and settings
  • Per-customer reports in PDF, Excel, Word, CSV or HTML
  • Scheduled reports each customer sets up for its own team
Who approves, in detail

Each customer can have its own approval chain for the same record, such as one level for a small customer and three for a large one, using role, team, reporting manager or saved-query approvers.

When the rules change

Bring your version of this.

A change a few months in is a reviewed release, not a rebuild. We will configure your version with you in a demo.

Book a demoAll use cases

Release: Customer: a clinic chain

Fields · Booking
Added: + Insurance number (required)
Approvals · Cancellation
Unchanged: None
Added: + Clinic manager
  1. Developmentmake the change
  2. QAreview the diff, test it
  3. Productionpromote the release
Illustration.