Weaion Labs is a four-person engineering practice. We do consultation, ERP, cybersecurity, automation, app development and web development, and we stay accountable for the whole of it. Most of these problems do not respect the boundaries between them, so neither do we.
Six service lines, drawn on one sheet because they overlap on most real engagements. Ask for one and you get the practice behind it.
The work that happens 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 out-of-the-box model does not fit how your market actually 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 repetitive 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.
Detail A-102.1
One route through the systems you already run. The trigger, the condition and the human approval are the part most automations leave out.
Scroll the diagram sideways →
Over 10k routes to human approval. Under 10k writes straight to the ERP.
Five stages, the same every time. The stage you are in is always written down, so neither side is guessing.
Thirty minutes, free, no pitch. You describe the problem in your own words. If we are the wrong people for it, we will tell you so, and usually tell you who is right instead.
Output: a straight answer about whether to continue
We come back with what the work actually involves: the parts that are certain, the parts that are risky, 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, and 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, when there is nothing left to do about it.
Output: something running, every fortnight
Documented, trained, and transferred to your people. 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 phone number
Four kinds of client, one practice. Find the note that matches the problem in front of you.
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 A fixed-scope first phase, then a decision on what comes next.
You need engineering that ships on a venture timeline without inheriting our bad habits. Direct access to the people writing the code, weekly releases, and estimates you can put in a board update.
Typical shape An embedded lane of the practice on your roadmap, weekly.
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 with sign-off gates and a documented handover pack.
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.
Detail A-104.1
A short, anonymised record of what we have found in live assessments. Client names and system details are withheld; the pattern is what matters.
F-01
[One sentence: what was exposed. No client name.]
F-02
[One sentence: what was exposed. No client name.]
F-03
[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.
Why one team rather than three vendors
Four people. Names are being added; the roles are already fixed because the work is already shaped around them.
Fixed price for a project 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 phone call reaches whoever is closest to 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 project, yes. Where the problem is still unclear we will tell you 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.