Getting the requirement clear
Work with the people who actually do the job to write down the real process, then fix scope and price stage by stage.
YOUR BUSINESS · YOUR WORKFLOW · YOUR SOFTWARE
Custom software
Software built around the way your business already works.
When a business runs a process too specific for packaged software, AQP builds it: internal systems, web and mobile applications, or the layer that joins disconnected systems into one flow of work. AQP delivers this service under the CommaDesk brand, with the same team and the same maintenance commitment after handover.
01Who it is for
Who this is for
Businesses whose own processes do not fit packaged software, or who are currently joining disconnected systems together by hand and by spreadsheet.
If you recognise yourself in the description below, this is the right solution to look at.
LeadershipOperations directorHead of ITDepartment headsDigital transformation leadTeams taking over a legacy system
02Challenge
What this solution handles
01
Packaged software forces the business to change the processes that make it work
02
Manual steps and loose spreadsheets are scattered across departments
03
Legacy systems have no API, so the same data gets entered several times in several places
04
A digital product idea has no scope, architecture, or roadmap concrete enough to start from
05
An AI experiment is hard to turn into software that runs reliably and securely in production
06
A system built by someone else is no longer supported and has no documentation to continue from
03 · What you get
What you get
These are the concrete changes in day-to-day work once the system is running.
01
Software that runs the business's process, rather than the other way round
02
Manual data entry and loose spreadsheets removed from the workflow
03
Something real in use at each stage, instead of waiting until the end of the project
04
Source code and documentation held by the business, as agreed in the contract
05
A team that keeps maintaining and extending the system after handover
06
Scope and cost agreed before each stage, so nothing runs away
04 · What gets installed
What gets installed and used
All of it is configured by us around your existing setup before handover.
Internal web systems
Orders, stock, people, assets, work and approval flows, following the way the business already operates.
Mobile applications
Apps for teams working away from a desk: attendance, sign-off photos, work records, usable with no signal.
System integration
Connect accounting software, ERP, cameras and loose files so nothing has to be entered twice.
Reporting & dashboards
Pull figures out of several systems onto one screen a manager can open and understand.
AI applied to the process
An assistant over internal documents, form and paperwork handling, or image analysis — only where AI genuinely removes work.
Maintenance & upgrades
After handover, the team keeps fixing, updating and extending the system under contract.
Taking over a legacy system
Take on software built by someone else, read the architecture, document it, and continue development.
05 · Use cases
SOFTWARE ENGINEERINGWhere it is already used
Transport & logistics
Trip management, dispatch, delivery, and connecting fleet data to accounting and ERP.
Manufacturing
Track production orders, equipment, maintenance and materials the way each plant actually runs.
Retail & chains
Manage branches, orders, customers, and consolidated reporting across many outlets.
Construction & property
Manage projects, quantities, handover records, residents and building services.
Field services
Dispatch technicians, issue work orders, capture site photos and confirm completion.
Public bodies & organisations
Digitise case handling, approval flows, and management dashboards.
06 · Service packages
Service packages
Cost depends on scale, how recordings are stored, and the support level. We survey first and then quote specifically — the survey is free.
Fixed-scope project
Suited to work where the requirement and the deliverables are already reasonably clear; priced by features, integration and time.
Stage by stage
Scope and price agreed for each stage, with the business deciding whether the next one goes ahead.
Dedicated team
A product and engineering team working with the business monthly against an agreed roadmap.
Maintenance & upgrades
A post-handover package covering fixes, updates, technical support and further development at the chosen level.
Scope, architecture, technology, timeline, cost and source-code ownership are established after the requirements-clarification stage and set out in each project's contract.
07 · Frequently asked questions
Before you ask
Can we start without a requirements document?
Yes. The team surveys the work, sits with the people who do it, and writes the requirement, scope and roadmap together with the business.
Can you continue developing the system we already use?
Yes. AQP reviews the source, architecture, documentation and infrastructure first, then proposes continuing, integrating, or rebuilding only what needs it.
Does the business own the source code?
For bespoke development, source code and documentation can be handed to the business. This is set out explicitly in the contract for each engagement model.
Can it be deployed on our own servers?
Yes. The system can run in the cloud, on the business's own servers, or a combination, according to security requirements and existing infrastructure.
How soon is there something we can use?
We hand over the part that matters most first, so the business can use it and comment early, while changes are still cheap. The specific milestones are agreed in the roadmap.
Who supports it after handover?
AQP's team continues maintenance at the chosen level: fixes, updates, technical support and further development.
Are CommaDesk and AQP different companies?
CommaDesk is the brand AQP uses for its software development service. Same team, same contract, same maintenance commitment.
Technical specifications
Technical specifications
This part is for your IT team. If you do not need it, skip it — we handle this side.
System architecture
01Survey & clarify
Take in the objective and survey the process, data, users, bottlenecks and the systems involved.
→02Design the scope
Define modules, interfaces, architecture, backlog, a staged roadmap and acceptance criteria.
→03Build in stages
Develop frontend, backend, mobile and AI in increments; test function, integration, performance and security.
→04Integrate & deploy
Connect systems, migrate data, and deploy to the cloud, the customer's servers, or a combination.
→05Hand over & stay on
Train users, hand over source and documentation as contracted, then keep maintaining and developing.
Protocols & systems it connects to
ERP / CRM / HRAccounting / POSTMS / WMSREST API / GraphQLWebhook / WebSocketMQTT / IoTCamera / VMSAQP Vision™ PlatformAQP Fleet™ OneGoogle WorkspaceMicrosoft 365Database / ETLSSO / OAuth 2.0
DESIGN FOR YOUR OPERATION
Get a quote for your case
Tell us how many locations or how many vehicles, and we will survey and send an approach with pricing.
Discuss your project↗