Product development

We build SaaS products for other businesses

Cube Systems runs four platforms and a handful of smaller apps of its own. The same team will build yours - from an idea, from a system that only works for one customer, or from a platform that has outgrown the way it was written.

Building software for one business and building software a thousand businesses can subscribe to are different jobs. The second one has to handle customers who never meet, signups at two in the morning, billing that reconciles itself and releases that do not need a maintenance window - and almost none of that is visible from a feature list.

We know because we have done it for ourselves. CubeERP, CubeCRM, CubeHR, CubeMSP, Kept, Trophy and Signed are our own products, carrying our own customers, and everything we would tell you about tenancy, pricing or onboarding comes from having lived with the consequences of getting it wrong.

Where people start

Four versions of the same conversation

Most product work begins in one of these four places. Which one you are in decides what the first three months look like.

  • An idea, and nothing built yet

    You know the problem and you know who has it. What you need is somebody to decide what the first version is, build it, and get it in front of paying customers.

  • A system that only serves one customer

    The software works. It is just installed on somebody’s server, or hard-coded to one business, and it cannot be sold twice without a rewrite.

  • A platform that has become expensive to change

    The product is live and customers like it, but every new feature costs more than the last and the roadmap has quietly stopped moving.

  • A market, but no product to sell it

    You already have the audience - members, franchisees, a customer base - and you want software to sell them under your own name, without becoming a software company.

How it happens

How a build actually runs

Five stages, each priced before it starts, and each one leaving you with something you own. You can stop at the end of any of them.

  1. Shape

    A few sessions working out what the product is, who pays for it and what the first version has to do. You leave with a written scope and a price, whether or not you go further.

  2. Design

    Screens, flows and the data model behind them, agreed before anybody writes production code. Changing a decision here costs an afternoon rather than a month.

  3. Build

    Two-week cycles with something working at the end of each one, in an environment you can log into. No six-month silence followed by a reveal.

  4. Launch

    Billing live, onboarding tested, monitoring in place, and the first real customers on the platform with somebody watching closely.

  5. Run

    Hosting, support and continued development for as long as you want it - or a clean handover to your own team, with everything documented.

Product development

Tell us what you want to sell

Not a feature list - the customer, the problem and why they would pay. We will tell you what a first version looks like, roughly what it costs, and whether we are the right people to build it.