How We Work
Five stages from first conversation to full hand-over, with a decision at the end of each, an NDA before details and the work assigned to you.
The process
Five stages, a decision at the end of each
You can stop after any stage and keep everything produced so far. Most clients go on because each stage removes risk from the next.
- 01
Discovery
A free conversation about the problem, the constraints and what success looks like.
→ scope note - 02
Feasibility
Research, calculations and bench tests on the riskiest assumptions first.
→ feasibility report - 03
Design
Architecture, schematics, software design and a fixed plan for the build.
→ design package - 04
Prototype
Working hardware and software, tested against the requirements and revised until it passes.
→ tested prototype - 05
Hand-over
Everything you need to own it: source, design files, documentation and support.
→ full hand-over
Deliverables
What you hold at the end
The goal is a product you own completely, not one that only we can maintain.
Source code
Firmware and software, in your own repository, with its history.
Design files
Schematics, PCB layouts, enclosure drawings and the bill of materials.
Test results
What was tested, how, and the results against each requirement.
Documentation
Build, deployment, user and maintenance documents.
Working hardware
The prototypes or pilot units built during the project.
The road ahead
Known limitations and recommended next steps, in writing.
Confidentiality & ownership
Your idea stays yours
NDA first
We sign a non-disclosure agreement before you share anything confidential, using your agreement or ours.
IP assigned to you
The work created for your project is assigned to you on payment, as written in the agreement.
Your data handled carefully
Documents and data you share are used only for your project, kept on access-controlled systems, and returned or deleted at the end on request.
No surprises
Scope, milestones and price are agreed in writing before work starts. Changes are quoted before they are made.
Engagements
Three ways to work together
Hours to days
Consultation
Expert advice on a specific technical question.
- Design, schematic or code review
- Feasibility opinion on a new idea
- Vendor and build-or-buy assessment
- Written findings and recommendations
Fixed scope
Project
A defined build, from specification to hand-over.
- Agreed scope, milestones and price
- A working prototype or production-ready result
- Progress demonstrations at each milestone
- Full hand-over of source and design files
Ongoing
Retained R&D
An engineering team on call for your product roadmap.
- Reserved engineering time each month
- Continuous development on a product line
- Priority support for what we built
- Regular roadmap reviews
Questions
About the way we work
How do we start?
Send a short description through the project form. An engineer replies, usually within two business days, to arrange a free call. If you need an NDA first, choose that option on the form.
Can we stop after the feasibility stage?
Yes. Each stage is agreed and paid for on its own, and you keep everything produced up to that point.
How do we follow progress?
Through milestone demonstrations, written updates, and shared access to the repository and documents as the work develops.
How are invoices handled?
Invoices come from the SAS Enterprises billing system and can be paid online; the invoice email includes a secure payment link. You can also check an invoice or ticket on the Check Status page.
What happens after hand-over?
That is up to you. Many clients keep a support arrangement or a retainer for the next version; others take the work in-house with the documentation we provide.
Have a hard technical problem?
Describe it in a few sentences. An engineer, not a salesperson, will read it and reply, usually within two business days.