Book a Technology Review

Home/Case studies/PaidDesk

Case study · Software & fintech

An accounting platform, built to be owned rather than rented.

PaidDesk sells accounting software on a one-time licence in a market that has standardised on monthly subscriptions. We built both halves: the product, and the platform that sells it.

What did GTX Digital build for PaidDesk?

Both halves of the business. The product is a multi-tenant web application covering invoicing, quotes, recurring billing, credit control, CRM, supplier records, statements, reporting, payroll, a customer portal and an in-app assistant — a custom PHP and SQLite build with Stripe Connect, so every customer takes card payments into their own Stripe account and PaidDesk never holds client money. Alongside it we built the marketing site and the search architecture that sells the licence.

  • Multi-tenant from the database up, with role-based capabilities.
  • Two-step sign-in: password, then a six-digit code sent by email.
  • Customers connect their own Stripe; PaidDesk is never in the money flow.

The brief

A product, not a project.

PaidDesk began as an internal invoicing tool built for one business. It worked well enough that the obvious question followed: could it be sold to other businesses?

That is a much harder question than it sounds. A tool that assumes one company and one user has no notion of tenancy, no roles, no sign-up, no billing of its own and no security model worth the name. Turning it into something you can sell means rebuilding the foundations underneath a working application without breaking the thing that already works.

And the commercial model made it harder still. Selling a one-time licence, rather than a subscription, means the software has to be supportable and upgradable long after the sale — so the architecture has to carry its own migrations, its own defaults and its own recovery, because nobody is standing behind it with a deployment pipeline every week.

  1. Modules Twenty-plus Invoicing, quotes, recurring, credit control, CRM, suppliers, statements, reports, payroll, portal, audit and more.
  2. Payments Stripe Connect Each customer’s own Stripe account, so PaidDesk never becomes the merchant of record.
  3. Licence One-time A single purchase plus an annual renewal, in a market that assumes a monthly subscription.

What we built

Six things that turned a tool into a product.

The accounting features are the visible part. What makes it sellable is underneath them.

  1. Multi-tenancy from the database up

    An accounts table as the tenant boundary, users bound to an account, a platform-admin layer above it, and a capability check on every action rather than a role string compared in a template. Self-service sign-up creates the account and its owner in one step.

  2. The accounting core

    Invoices and line items, quotes, recurring schedules, payments and payment events, customers, suppliers with file attachments, statements, reporting and an append-only audit log — with PDF generation for every document a business needs to send.

  3. Stripe Connect, the right way round

    Customers connect their own Stripe account by OAuth. Invoices carry a pay-by-card link, webhooks confirm the payment and the ledger records it. PaidDesk is never the merchant of record and never holds client funds — which is both the honest architecture and the one that avoids becoming a regulated money business.

  4. Credit control that chases on its own

    A reminder ladder from invoice to reminder to overdue to follow-up to paid, with per-invoice de-duplication so nobody is chased twice for the same thing, and customer statements that can be emailed straight from the page.

  5. An assistant that acts, carefully

    The in-app assistant can draft an invoice or quote, convert a quote, record a payment or run the recurring batch from a sentence of instruction. Anything it creates is saved as a draft: it prepares the work, a person sends it. That was a deliberate reversal of an earlier build that sent directly.

  6. Installable, and secure by default

    A progressive web app with its own manifest and service worker, so it installs on a phone or a desktop. Sign-in is password plus a six-digit emailed code, hashed with a ten-minute expiry and an attempt cap, lockout after repeated failures, and an optional thirty-day trusted-device token for people who sign in daily.

How it was built

How we built something sellable.

A product is judged on the things a project never gets asked about: what it refuses to do, and what happens when nobody is watching.

  1. Refuse the features you cannot do properly

    No bank feeds, no Open Banking, and no suggestion anywhere that PaidDesk holds your money. Each of those would have made a better feature list and a worse product. A capability you cannot support honestly costs more in support and reputation than it earns in sales.

  2. Security as a feature, not a hardening pass

    Two-step sign-in, lockout, trusted devices, capability checks on every action, an audit log, the raw database closed off from the web, public sign-up controlled and every output escaped. A product that holds a company’s invoices is a target from day one.

  3. Migrations that run themselves

    Schema changes apply on boot rather than from a console someone has to remember to open. A licensed product lands in installations you do not administer, so it has to be able to upgrade itself and heal its own missing rows.

  4. Price the product, then build the page around it

    A one-time licence is an unusual claim in this market, so the site’s main job is answering “what is the catch”. The pricing, the renewal and the Stripe arrangement are stated plainly rather than buried, because the objection is the sale.

  5. One template, every page

    A master template takes a page’s data and emits the head, the structured-data graph, the breadcrumb, the quick answer, the body, the related links and the FAQ. Clean URLs are physical directories with their own index, so there is no router to go wrong. A markup change is one edit.

  6. A search architecture for a software buyer

    Feature pages for the thing being compared, industry pages for the trade doing the comparing, and location pages where the search has local intent — each answering its question in the first eighty words, and the crawlers that feed AI assistants let in deliberately rather than by accident.

Results

What we will and will not claim.

PaidDesk is a product in market. Its commercial numbers are the client’s to publish, not ours.

What is verifiable is the build: a multi-tenant application with the module range listed above, Stripe Connect in production, UK PAYE, National Insurance and pension calculation in the payroll module against current-year rates, and a marketing site with a feature, industry and location architecture behind it.

What we will not do is put a revenue figure, a customer count or a review score on this page. PaidDesk is sold on a one-time licence to UK businesses, and inventing traction for a product in its first years is the fastest way to make a genuinely good piece of software look like vapour.

For the client to supply

Figures we would publish

  • Licences sold, and the trial-to-paid conversion rate behind them.
  • Support ticket volume per hundred active accounts.
  • Organic impressions and clicks for the feature and industry clusters.
  • Uptime and error rate from the production logs.

The judgement call

The assistant drafts. A person sends.

An assistant that can create an invoice is a nice demonstration. An assistant that can send one is a liability, and we shipped that version first.

The reasoning for sending directly was reasonable enough: the user asked for an invoice, so give them a finished invoice. The problem is the failure mode. A misread amount, the wrong customer picked from a similar name, a duplicate of something already sent — and the mistake is not in a draft the user can glance at, it is in a client’s inbox with your company name on it. Accounting software is the last place to be clever about this.

So the behaviour was reversed. The assistant does the work — reads the request, finds the customer, builds the lines, calculates the total — and stops at draft. The human cost is one click. The alternative cost is a client relationship, and the user made the right call asking for the change.

Where we drew the line

Automation with a stop

  • The assistant can draft, convert, record and schedule.
  • Anything leaving the business stops at draft for review.
  • Every action it takes is written to the audit log.
  • Payroll is restricted to the owner, not the role that handles invoices.

Questions

The PaidDesk build, answered.

What people ask when they are considering a product build of their own.

Ask us a question Email us

What did GTX Digital build for PaidDesk?

The accounting application and the site that sells it. The application is a custom multi-tenant build covering invoicing, quotes, recurring billing, credit control, CRM, supplier records, statements, reporting, payroll, a customer portal and an in-app assistant, with Stripe Connect for card payments and PDF generation for every document. The site adds the marketing pages and a feature, industry and location search architecture.

Is PaidDesk a payment processor?

No, and that is deliberate. Each customer connects their own Stripe account, so card payments go directly to them. PaidDesk creates the checkout and records the result, but it is never the merchant of record and never holds client funds. Building it the other way round would have made PaidDesk a regulated money business, which is a different company.

Does it connect to my bank?

No. There are no bank feeds and no Open Banking integration, and we advised against claiming otherwise. It would be a popular feature and we may build it properly one day, but a half-built bank connection in accounting software is worse than none — people reconcile against it and trust the result.

How can accounting software be a one-time licence?

Because of how it is built. A self-contained PHP and SQLite application does not carry the per-tenant infrastructure cost that makes a monthly subscription unavoidable, and schema migrations that run on boot mean an installation can upgrade itself. The licence covers the software and the annual renewal covers updates. It is a real architectural choice, not a pricing gimmick.

Can you build a product like this for us?

Yes, and the honest version of that answer starts with whether you should. Turning an internal tool into a sellable product means building tenancy, roles, sign-up, security, support and self-upgrade — usually more work than the features you already have. It pays off when there is a real market for the tool. We will give you our read on that before quoting the build.

What does multi-tenant actually mean here?

That each business using the software is a separate account at the database level, with its own users, its own roles and its own data, and that a platform-admin layer sits above all of them for support. It is the difference between software you can sell to a hundred companies and software you have to deploy a hundred times.

Client voices

What clients say.

  • GTX Digital has been brilliant to work with. They took the time to understand what we needed and built a solution that actually works for the business. The communication has been excellent throughout and it’s clear they understand both the technology and the commercial side.

    Tony ShinglerOmnia Resourcing
  • Really impressed with GTX Digital. They took the time to understand how our business works before recommending a solution. The whole process was clear, professional and much easier than expected.

    James Wilson
  • GTX Digital helped us connect several systems that were previously working separately. It has saved our team a lot of manual work and made our processes much more efficient. Great experience overall.

    Daniel Harris
  • We needed a bespoke software solution for our business and GTX Digital understood exactly what we were looking for. The communication throughout the project was excellent and the finished system works really well.

    Sophie Mitchell
  • Very professional team. They took the time to understand the problem before suggesting a solution, which we really appreciated. Everything was explained clearly and the project was handled extremely well.

    Michael Thompson
  • GTX Digital made a complicated technology project feel very straightforward. They kept us updated throughout and were always available when we had questions. Very happy with the final result.

    Oliver Bennett
  • We approached GTX Digital to replace an outdated system and they handled the whole process brilliantly. The new platform is much easier for our team to use and has made our day-to-day work considerably smoother.

    Emily Carter
  • Really good experience from start to finish. The team listened to what we needed, explained the technical side in simple terms and delivered a solution that works perfectly for our business.

    Ryan Edwards
  • GTX Digital helped us automate several repetitive tasks that were taking up far too much of our team’s time. Their approach was practical and the improvements have made a noticeable difference.

    Charlotte Morgan
  • We had several systems and APIs that needed to work together, and GTX Digital handled the technical side extremely well. They were organised, responsive and professional throughout the project.

    Thomas Cooper
  • Very happy with the service from GTX Digital. They didn’t try to sell us things we didn’t need. Instead, they focused on understanding our business and finding the right solution.

    George Richardson
  • GTX Digital helped us turn an idea into a working digital platform. The team were knowledgeable and easy to communicate with, and they made sure we understood everything throughout the development process.

    Hannah Walker
  • Excellent experience with GTX Digital. The project was well organised and we always knew what was happening next. The final system has made our internal processes much more efficient.

    Jack Anderson
  • We needed a technology partner who could understand both our business requirements and the technical side of the project. GTX Digital were a great fit and delivered exactly what we needed.

    Lauren Parker
  • The team at GTX Digital were fantastic to work with. They took a complicated requirement and broke it down into manageable stages. The final solution has saved us a lot of time and reduced repetitive work.

    Ben Foster
  • Highly recommended. GTX Digital combines strong technical knowledge with a very practical approach to business problems. Communication was excellent and we were very pleased with the finished product.

    Olivia Collins

Services used

What this build drew on.

  1. Build

    SaaS Products

    Multi-tenant products with billing, onboarding and the admin tooling to run them.

    Explore
  2. Build

    Bespoke Software

    Operational systems written for one business, not licensed to a whole market.

    Explore
  3. Connect

    Customer Portals

    Self-service for customers, so routine questions stop arriving by phone.

    Explore
  4. Connect

    API Development

    APIs and integrations so data is entered once and moves on its own.

    Explore

All 19 GTX Digital services

Next step

Thinking about turning a tool into a product?

The build is the easy half. We will tell you what tenancy, security and self-upgrade actually cost before you commit to the idea, and whether the market you have in mind is really there.