One workflow, two sides of it. Clients scope work as structured data and pay per accepted milestone. Engineers get matched on evidence, propose a methodology and get paid as milestones are accepted.
The work of hiring an engineer is mostly the work of writing down what you actually need. The intake does that structurally, and everything downstream — matching, proposals, acceptance, payment — reads from it.
The intake asks what an engineer would ask: discipline, asset, governing standard, jurisdiction, input files you already hold, whether professional sign-off is required, and who owns the resulting IP. Anything you leave blank is recorded as unspecified rather than assumed. If your need is small and well understood, skip the brief and buy a fixed-scope service instead.
Matching runs over structured fields, not keyword similarity. Each candidate is scored on discipline, named software, cited standards, industry history, jurisdiction, current availability and verified licence status — and every axis shows the reason it did or did not meet your requirement. A low score on jurisdiction with a high score everywhere else is a different decision than the reverse, so the breakdown is visible rather than rolled into one number.
Proposals arrive normalised into one table: methodology, assumptions declared, software and version, standards applied, deliverable list, exclusions, milestone plan, schedule and price. Because every engineer answers the same structured questions, you are comparing approaches rather than writing styles. Exclusions are shown as prominently as inclusions.
You fund a milestone, not the whole contract. Funds sit in escrow and are released only against a deliverable you have accepted on written acceptance criteria agreed before the work started. Hourly contracts use tracked time with a weekly cap you set. Nothing leaves escrow on a schedule — only on acceptance.
A workroom opens on award: versioned file transmittals with revision history, a formal RFI log, drawing and document approvals, model and calculation review threads with comments anchored to a specific revision, and a change request flow that states cost and schedule impact before any extra work begins. Scope changes are decisions with a record, not messages that get lost in a chat log.
Review the deliverable against the acceptance criteria. Accept, or request a revision within the agreed revision allowance. Acceptance releases that milestone's funds. Reviews are scored separately on technical quality, accuracy, timeliness, communication, documentation and scope management — because an engineer who is strong on analysis and weak on documentation should be legible as exactly that.
The four modes differ mainly in who decides the method and how much is fixed before money moves. Choosing the wrong one is the most common reason a technical engagement goes badly.
Best for A drawing set conversion, a single load calculation, a DFM review, a report check
Watch out Unsuitable once scope depends on files nobody has looked at yet
OpenBest for A design package, a full analysis campaign, anything needing a methodology decision
Watch out Requires you to answer the structured brief properly to get comparable proposals
OpenBest for Ongoing advisory, a niche specialisation, continuity with someone who knows your asset
Watch out You are not comparing alternatives, so validate the rate against the market yourself
OpenBest for Coordinated disciplines, professional indemnity cover, work heading toward sign-off
Watch out Higher minimum engagement; procurement and insurance checks take time
Open| Mode | Who defines the method | Scope fixed at | Payment structure | Typical engagement size | Sign-off path |
|---|---|---|---|---|---|
| Buy a Service | The engineer, published in advance | Purchase | Package price, escrowed, released on acceptance | $150 – $5,000 | Not included; buy a separate review or sign-off scope |
| Post a Project | Proposing engineers, you choose between methods | Award | Milestones or tracked hourly, escrowed | $2,000 – $250,000 | Can be a named milestone with a registered professional |
| Find an Engineer | Agreed one to one | Contract or retainer start | Hourly, fixed or monthly retainer | $500 – $60,000 | Only if that engineer holds the relevant registration |
| Hire a Team or Firm | The firm, against your requirements | Phase gates within a programme | Phased milestones, rate card or programme fee | $25,000 – $2m+ | Usually in scope, under the firm's insurance and registrations |
Engagement sizes are typical observed ranges and are indicative only. Sign-off, where required, always depends on a professional registered in the relevant jurisdiction — see the professional disclaimer.
Whichever mode you use, the same four systems carry the engagement.
Disciplines, specialisations, deliverables, software, standards, industries and project scale are fields, not free text. That is what makes matching explainable and filtering precise.
Identity, education, registration, certification, portfolio ownership, references and expert review are separate checks with separate badges — never one undifferentiated tick.
Revision-controlled transmittals, RFI logs, document approvals, review threads anchored to revisions, and priced change requests.
Milestone funding, written acceptance criteria, a bounded revision flow and a documented resolution process with defined response windows.
Post a brief and let qualified engineers propose a methodology, or build a profile that makes your evidence legible to the clients who need exactly your specialisation.
