Build software to sell

We design and build the software. You publish it under your own name.

Need a device with it? We design the circuit board too.

A software system in layers, with a device when neededA software system drawn as layers under one specification: the screens people use on the web and on a phone, above the service that holds the accounts, the data and the billing, above its connections to payments, email and an accounts package. Below them, drawn lighter and dashed, a device layer with a circuit board, for a product that needs its own ESP32 or STM32-based circuit board.Screensweb and phoneServiceaccounts, data and billingConnectionspayments, email, accounts packageDevicebespoke ESP/STM32-based PCBsOne specification
  • A written specification before anything is built
  • You know what you own before we begin
  • A small first version, then more

Who this is for

A founder with a software idea
You have the idea and the customers in mind. You need it designed and built, starting small.
A professional turning know-how into a product
You do something well for clients. You want a product that does part of it without you in the room.
A business with an internal tool others would pay for
The tool already works for you. You want it built properly so you can sell it.
An agency or consultancy adding a product
You have clients and a brand. You need a build partner behind it.

What kinds of software

Each starts as a written specification. Systems for your own organisation’s use are on the Software page.

Web apps with accounts and subscriptions

A service people sign up to in the browser, with plans they pay for.

The specification covers accounts and roles, what each plan includes, what is sent and when.

Phone apps for iPhone and Android

An app your customers install, usually with a web service behind it that holds their accounts and data.

The specification covers the screens on each phone, what works without a signal, the notifications, and what each store listing needs.

A customer portal sold as a product

A place where your customers’ own clients log in to see their records, documents and progress, sold to each business that uses it.

The specification covers who sees what, how each customer’s data is kept apart, and how a new customer is set up.

An integration or connector that other software uses

A connector that moves information between systems, sold to the people who use them.

The specification covers what passes in each direction, what happens when one side is unavailable, and how keys are kept.

The route from idea to launch

Seven stages, each marked with who does it. We tell you what each involves before it starts.

  1. The brief

    Together

    We ask what the product does, who will pay, how you will charge, and where people will use it.

  2. The specification

    Us

    We write down what the first version includes and what it does not, the accounts and roles, how people pay, the data held, and how each requirement will be tested. You agree it before anything is built. A quote comes with it.

  3. The first version

    Us

    We build in stages, with working versions along the way, discussed against the specification.

  4. Testing

    Together

    We test against each requirement and write up the results. You try it with real people before it goes public.

  5. The handover

    Us

    You receive the source code, the documentation and the test records, and we set up the system for you to run.

  6. Publishing

    You, with our guidance

    Store listings, review by the stores, legal pages and company set-up. We tell you what each needs.

  7. Selling and support

    You

    Finding customers, taking payment, and answering your users.

Nothing is built before the specification is agreed. How we work

What publishing involves

What sits around the software once it is ready to go public, and who usually does it. We go through it with you while we write the specification.

What it isWhat it usually needsWho does it
Accounts for the app storesYour company registers with each store and pays its fee, then adds us to the account so we can build and prepare releases for you. The app goes out under your company’s name. We tell you what each store asks for before you start.You, with our guidance
Privacy and personal dataA privacy notice, and a clear list of what personal data the product holds and why. UK data protection law applies, and some organisations have to pay the ICO’s data protection fee. The ICO has its own check for this.You, with our guidance
Taking paymentA payment provider account in your name, and a clear view of each store’s rules on how you may take payment. We check this during the specification.You, with our guidance
Terms and legal pagesTerms of use and a privacy notice written for your product. These need a lawyer’s review.You
Security and hostingWhere the product runs, how it is backed up, and who can see what. We set out what we have designed and what you must keep doing.Together
Support and running costsYour users will have questions, and hosting and payment fees are ongoing costs.You

What each store and the ICO ask for

Why start small

A first version that does one job well is cheaper to build and easier to test than a full product. We will tell you what we would leave out of version one, and what we would build first.

What you receive

  • The written specification
  • The source code
  • The documentation
  • The test records
  • The design files for any device

Agreed in writing before work starts

Who owns the source code, the designs and any parts we reuse from earlier work is written into the agreement before work starts. We do not begin without it.

The store accounts are in your company’s name, and we are added to them.

Questions

Can we start from a rough idea?

Yes. We begin with a conversation, then write the specification.

What do we have to do first?

Tell us what the product does, who will pay, how you plan to charge and where people will use it. The enquiry form asks for these, and the product brief sets them out to fill in.

Who owns the code?

That is agreed in writing before work starts.

Who holds the store and payment accounts?

Your company. It registers with each store, pays the fee and adds us to the account, so the app goes out under your name.

Do you build phone apps?

Yes, for iPhone and Android, as well as web apps.

Do you market it or run it for us?

We design and build it and hand it over. Marketing and support after sale are yours, and we say what each needs.

If your product includes a device

Some products need a device of their own: a sensor, a reader or a controller that the software works with. We design the circuit board and the enclosure with the software, and the route then has stages of its own.

Hardware

Who it suits

A company adding a product to its range
You know your customers and have a way to reach them. You need the product designed and built.
A maker of equipment that wants it connected
Your machines or devices work well. You want sensors, a connection or an app added, and you have a manufacturer already.
A founder with a product idea
It needs software and hardware designed together, and you want the specification written before money is spent on building.
A business that has been asked for hardware
Your customers want a device with your software, and you have no one to design it.

The route to market

Getting a product with a device to market has eight stages. We do the first five. The next two are separate work, and the last is yours. We tell you what each involves, so nothing arrives as a surprise.

  1. The brief

    Together

    We ask what the product must do, who will buy it, and how you plan to sell it.

  2. The specification

    Us

    We write down the requirements, how each will be tested, and how the software, board and enclosure fit together. You agree it before anything is built.

  3. The prototype

    Us

    We build working software, a circuit board and an enclosure that fit each other. The board is made and assembled by a board manufacturer we order from.

  4. Testing

    Us

    We test the prototype against each requirement in the specification and write up the results.

  5. The handover

    Us

    You receive the source code, design files, bill of materials, documentation and test records.

  6. Certification

    Separate work, agreed separately

    The tests and approvals a product needs before it can be sold.

  7. Manufacturing

    Separate work, agreed separately

    Making the finished product in quantity, including enclosures, assembly and packing. We can order the boards. The rest is agreed separately.

  8. Selling and support

    You

    Packaging, distribution, returns and help for your customers.

A product's route from prototype to marketA product travelling from idea to market across a sheet: a prototype board above its enclosure, the boxed product under an approval seal, a stack of boxes made in quantity, and a box on its way to a customer

Work that is separate

These are separate work and are agreed separately.

Certification
A product needs tests and approvals before it can be sold. What applies depends on what the product does and how it is powered.
Manufacturing
Making the finished product in quantity, including enclosures, assembly and packing. We can order the circuit boards, made and assembled by a board manufacturer. The rest is agreed separately, and whoever does it will need the handover files from the fifth stage.
Packaging and distribution
How the product is boxed, stored and sent, and what happens when a customer returns it.
Support after sale
Your customers will have questions, and someone has to answer them.

A product sold under your name generally makes you responsible for it as its producer. We set out what applies to your product when we write the specification, and you should take advice on your own position.

Questions about devices

Do you build the software and the hardware together?

Yes. They are designed as one system, with the joints between them written down.

Do you make the finished units?

Not the finished product. We can order the circuit boards, made and assembled by a board manufacturer. Enclosures, assembly and packing in quantity are separate work, and we give whoever does them the files they need.

Discuss your software

Tell us what the product does, who will pay for it and how you plan to charge. We will reply to arrange a conversation.

Write your product brief