The six questions
01
1. Domain
Automotive, defence and aerospace, semiconductor or embedded and industrial. It sets which standards and toolchains apply.
02
2. Standard
The standard the work must satisfy, for example ISO 26262 with a target ASIL, ASPICE level, DO-178C DAL, UVM sign-off criteria or IEC 61508 SIL. Choose "not sure" if it is still open.
03
3. Scope
What you need built, verified or fixed: a software component, a BSP, a testbench, a test campaign, a certification work package.
04
4. Team size
A rough number of engineers, or let us propose one from the scope.
05
5. Timeline
Start date and any fixed milestones, such as a SOP date, a tape-out, a certification audit or a customer release.
06
6. Engagement model
Fixed-scope project, staff augmentation or Build-Operate-Transfer. See engagement models if you are unsure.
What your scoping brief contains
- A summary of the work as we understand it, in engineering terms.
- The standards, artefacts and evidence the work is likely to involve, such as a safety plan, traceability matrix or verification plan.
- A suggested team shape: roles, seniority and the skills each needs.
- Assumptions, risks and the open questions to settle on a technical call.
- Next steps, including an NDA if detailed information is needed.
What happens next
The brief is drafted automatically and then reviewed by a Stalwart engineer, who contacts you to discuss it. It is a starting point for a conversation, not a quote or commitment. Please keep confidential and export-controlled details out of the form; we can go into them under NDA. How we use AI in this process is on the responsible AI page, and data handling is in the privacy policy.
If you need people rather than a project, request engineers instead.
Project Scoping Assistant
Frequently asked questions
Is the scoping brief a quote?
No. It is a structured summary of the work, the standards involved, a suggested team shape and the open questions. An engineer reviews it with you, and a proposal or quote follows once scope and assumptions are agreed.
What if I do not know which standard applies?
Choose "not sure". The brief will suggest the likely standards for your domain and product, for example ISO 26262 for road vehicle E/E systems or DO-178C for airborne software, and list what needs confirming. The ASIL calculator can also help.
Should I include technical documents?
Not at this stage. The form only needs a high-level description. Detailed specifications, code or anything export-controlled should be shared only after an NDA is in place, through a channel we agree with you.
Who reviews my brief?
A senior engineer from the relevant domain. They check the draft, correct anything the assistant got wrong and contact you to discuss scope, risks and how we would staff the work.