The four stages of a projectThe four stages of a project as layers: a written summary with a pencil, a specification with its checklist ticked and agreed, a working version on screen, and a tray holding the documentation, the test records and the boardSummarySpecificationWorking versionsHandoverAgreed before it is built

How we work

Every project runs in the same four stages, whether it is software on its own, a board on its own, or both, and you deal with the same person throughout.

Each stage leaves you holding something written down, so you can see where the project stands and nothing rests on memory.

Next: we learn the work

1We learn how the work is done today

It starts with a conversation about the problem and the people involved. Where it helps, we look at the spreadsheets, forms and tools already in use, and how information moves between them. We write up what we have learned so that nothing rests on memory.

What you will seeA short written summary of the problem, for you to check and correct.

Next: the specification

2You agree a written specification and a quote

The summary becomes a specification: what will be built, what will not, and how it will be handed over. For hardware it also covers what the board has to do and how it will be enclosed. Design and build work starts only once you have agreed it.

What you will seeThe specification, and a quote for the work it describes.

Next: the build

3We build in stages you can try

The system takes shape in stages, and each one can be tried before the next begins. Changes are discussed against the specification, so nothing grows without your agreement.

What you will seeWorking versions to try, and prototypes where there is hardware.

Next: the handover

4We hand over, then support

We set up the system, move across the data it needs and train the people who will use it. The design is documented at handover.

What you will seeThe live system, its documentation, the test records and the support arrangement.

Next: after handover

After handover

The design is written down
Documentation explains how the system works and how it is run, clearly enough for someone else to take it over. For hardware that means the schematic, the layout and the reasons behind them, as well as the firmware.
Support carries on
How problems are reported and how later changes are handled is agreed before handover, so there is no question about it once the system is live.

Next: questions

Questions

How long does a project take?

It depends on the size of the system. The timeline is set out in the specification and agreed with the quote.

How is a project priced?

With a quote for each project, based on its specification. No two systems are the same, so there is no price list, but each of the example systems carries indicative costs to show the scale.

Can a new system connect to the software we already use?

Often, yes. We check whether each connection is possible during the brief, before it goes into the specification.

Do we have to take software and hardware together?

No. Software on its own, a board on its own, or both: the specification covers whatever the project needs. Taking both together means they are designed to fit each other, but a software system does not need a board, and a board can be designed for software you already have.

What if a package would do the job?

Then we will say so. Custom software is worth it when the work does not fit the packages available, and not otherwise.

Discuss your requirements

Send a short description of the system you need and who will use it. We will reply to arrange a conversation.