Sheet A-000 / Rev 04 / Rate 25p
Call the deskWeaion Labs is a four-person engineering practice working one long shift: consultation, ERP, cybersecurity, automation, app development and web development. You hand over the problem once. The same four people carry it to the end.
Six cues in the order they run. Each one carries its own entry time and its own load. Open a cue to see what comes out of it.
The work before anything gets built. Process mapping, technology selection, build-versus-buy calls, cost modelling, and the honest answer when the honest answer is that you do not need this yet.
Bought when a decision costs more than the advice does.
Selection, implementation and rescue. Data migration that survives contact with your legacy, custom modules where the standard model does not fit how your market trades, integrations that talk to what you already run, and reporting your finance team trusts without a spreadsheet in the middle.
Bought when the system is the bottleneck, or the last rollout failed.
Assessment before you have an incident, not after. Vulnerability testing of the estate you actually run, hardening of infrastructure and endpoints, audit readiness, and incident response for the case where the worst thing is already happening and you need someone who has done it before.
Bought when an audit is coming, an insurer is asking, or you already got burned.
Mobile and internal applications that survive real use rather than a demo. Field tools that work with no signal, clean APIs behind them, and a release pipeline your own people can ship from without asking us for permission.
Bought when the existing tools do not fit the way your people actually work.
Websites, web applications and the integrations that hold them together. Fast, accessible, maintainable, and handed over with the keys, the accounts and the documentation. No page-builder subscription you are locked into for the life of the business.
Bought when what you are selling has to load fast and stay up.
The work between the systems: quote to invoice, enquiry to CRM, alert to ticket, stock movement to reorder. We map the route, build it on a workflow platform, add the retries and the audit trail, and hand over the keys.
Bought when people are copying data between tools, or a step is missed when someone is away.
Most of the work between your systems is still a person moving data from one window to another. We wire that route once, with a condition where a decision belongs and a human where judgement belongs.
Route 01 / quote to invoice
The trigger, the condition and the approval are the part most automations leave out. This one is documented, versioned and handed over, so you can change it without calling us.
Scroll the diagram sideways →
Over 10k routes to human approval. Under 10k writes straight to the ERP.
Five stages, the same every job. Each one closes with something written down, so nobody is guessing where the show stands.
Thirty minutes, free, no pitch. You describe the problem in your own words. If we are the wrong people we will say so, and usually name who is right instead.
Output: a straight answer about whether to continue
We come back with what the work actually involves: the certain parts, the risky parts, the parts that will cost more than you expect, and what it takes to reach a firm number.
Output: written scope, risk list, cost model
Fixed scope, fixed price, dated milestones, one named person on our side who owns it. No hourly surprises and no open-ended discovery phase that quietly becomes the invoice.
Output: a contract you can read in ten minutes
Short cycles. You see working software every two weeks, not a status report describing it. We tell you the moment something changes rather than at the end.
Output: something running, every fortnight
Documented, trained, transferred. You own the code, the accounts, the infrastructure and the documentation from day one. We stay reachable afterwards without pretending that is a retainer.
Output: your system, your keys, our number
Four kinds of client on the same desk. Find the one whose situation is in front of you.
Unit 01
You need it to work and you cannot fund a twelve-month programme. We scope tightly, phase the work so the useful part lands early, and tell you plainly what can wait a year.
Typical shape Fixed-scope first phase, then a decision on what comes next.
Unit 02
You need engineering that ships on a venture timeline without inheriting our bad habits. Direct access to the people writing the code, weekly releases, estimates you can put in a board update.
Typical shape An embedded part of the crew on your roadmap, weekly.
Unit 03
Procurement-ready documentation, a security position agreed before we start, change control, audit trails, and a clean handover to your own team or your incumbent vendor.
Typical shape Phased milestones, sign-off gates, documented handover.
Unit 04
White-label or subcontract delivery. Your client stays yours. We work to your standards and your documentation, and we have no interest in going around you to talk to them directly.
Typical shape Your contract, your relationship, our delivery.
A short, anonymised record from assessments we have run. Client names and system details are withheld; the pattern is what matters.
B-01Slot
[One sentence: what was exposed. No client name.]
B-02Slot
[One sentence: what was exposed. No client name.]
B-03Slot
[One sentence: what was exposed. No client name.]
Full notes are available under NDA. We do not name a client without written permission, and we do not publish a finding we have not closed or disclosed. Ask for the current notes.
Four people on this show. Names are still to be typed in; the roles are already fixed because the work is shaped around them.
Fixed price for a job with a written scope. Monthly where the work is continuous, such as maintenance or a standing security review. We will tell you which one you actually need instead of defaulting to billable hours.
One route in. An email reaches all four of us; a call reaches whoever is nearest the problem.
That is the normal case. We start by reading your current estate, because a greenfield build that ignores it is a second system to maintain rather than a solution.
Yes, and it is some of the most useful work we do. We audit what exists, write down what is actually true, then decide with you whether to finish it, rebuild part of it or replace it.
For a scoped job, yes. Where the problem is still unclear we will say that a fixed price would be a guess, and propose a short paid discovery stage instead.
You hold the code, the accounts, the infrastructure and the documentation from day one. Afterwards we are reachable for support, changes and the next piece of work.