flyingpenguinSOFTWAREShow me what you do now. I’ll help turn the awkward bit into a tool that fits the way you work.
An equipment enquiry becomes a specialist’s quotation, then a customer’s decision. Reformer Connect is one of the businesses I’ve built around that handover.
Try the sample journey below to see what moves from one person to the next.
Follow the exampleMore about this projectA service enquiry, from the first details to the customer’s decision.
Interactive explanation using sample details, based on Reformer Connect’s public journey. Nothing is submitted, quoted or booked here.
A studio owner describes the equipment and what needs looking at. The information stays with the job.
A structured request for a specialist to assess.
The form gathers the details needed for the handover in one place.
An engineer reviews the equipment and the work requested. They decide whether to offer a quotation.
A quotation the customer can review.
A job board and clear permissions give each person the information they need. The engineer chooses whether to quote.
The equipment owner compares the responses and chooses the engineer they want to proceed with.
The customer makes the appointment decision.
The software carries the information through the process. It does not award the work automatically.
A shared tool, a customer account or a connection between systems. We can start with the job, then choose what to build.
Internal tools for quoting, job tracking and the way the business works.
Accounts where customers can find their documents, requests and next steps.
Availability, requests and confirmations that suit the way you run appointments.
Join up repeated admin with clear checks and a person in control where needed.
Connect business systems with a defined job for each connection.
A custom feature for an existing site, or a suitable tool from the Flying Penguin catalogue.
Browser or mobile apps for a defined product, with the first release agreed at the start.
A prototype gives us something to try. We can see where the flow makes sense, what is missing and what belongs in the first release.
From first conversation to handoverThe people, information and decisions involved.
Use sample details and tell me where it gets awkward.
A written scope, cost and test list before production work.
Who owns the code? What does hosting cost? What happens when a connection fails? Those questions matter as much as the screens.
Scope, ownership and running costsIt depends on the tasks, screens, user roles, data and connections. We agree a defined scope and written quote before build work starts, including any paid discovery or prototype work.
Project work transfers on full payment, unless agreed otherwise in writing. Flying Penguin’s existing proprietary tools and third-party software retain their own ownership and licences. The proposal explains the handover.
That is often a useful starting point. We check the accounts, access, APIs and existing data before deciding what should connect, stay or change.
You speak to me, Garreth. I’m based in Nottingham and Derby and work with businesses across the UK.
Hosting, monitoring, backups, maintenance and future changes have an agreed owner and cost. They are written down separately from the initial build.
A task, a spreadsheet or an idea you want to work through. Describe it first and we can agree what to look at next.