how we work

FROM IDEA TO LAUNCH.

FAQ

  • Most projects take between six and twelve weeks, depending on scope. We share a clear timeline after our first call, so you always know what happens next.

  • Send us a short note about what you want to build. We will book a call, ask a few questions, and follow up with a proposal within a few days.

  • Yes. We often join in-house teams and adapt to your tools and schedule, whether you need a full project or extra hands for a few weeks.

  • Pricing depends on the size and complexity of the work. We provide a fixed quote after scoping, with no surprise charges along the way.

  • We do. Every project includes a support window after launch, and we also offer ongoing plans if you want us to keep improving things.

Why the name fits the process.

Phase margin is the buffer between a stable system and an unstable one. We plan projects the same way. Each phase keeps enough margin in schedule, budget and design that a problem shows up early, as a decision for you to make.

Start with a feasibility and cost study.

One to two weeks, one fixed price. Bring sketches, a description, a prototype that almost works, or a problem nobody has solved. An engineer who would build it reviews it and tells you plainly what it will take.

Use the report to raise money, gain internal approval, or decide the project isn't worth further resources. All three are good outcomes.

Deliverables

  • Technical feasibility assessment. What is proven, what is uncertain, and what has to be tested first.
  • Architecture sketch. The major parts, protocols and interfaces, and how they connect.
  • Risk list. Ranked, with the test that would retire each one.
  • Cost estimate. Rough engineering cost, unit BOM cost, and operating cost where relevant.
  • Timeline and recommended next phase. With a fixed quote, so you can start immediately if you choose to.

Then we build or deploy in phases.

Products follow the build track. Systems that go into a hospital, a venue or a secure facility also follow the deploy track. Many projects use both.

PhaseWhat happens and what you get
Architecture and designRequirements, schematics, mechanical concepts, software architecture, test plan. You get a design review package and a locked plan for the prototype.
Prototype (EVT)First working boards, firmware and software, tested on the bench. You get working units and a test report.
Design verification (DVT)Production-intent design, standards pre-testing, reliability testing. You get verification data against every requirement.
Validation and regulatoryHuman factors, clinical studies and submission files where needed. You get the evidence a regulator or customer will accept.
Production transfer (PVT)Pilot builds with your manufacturer, test fixtures, work instructions. You get a product your manufacturer can build without us.
Sustaining supportUpdates, fixes, component changes and new features.
PhaseWhat happens and what you get
Site surveyWalk the site, measure RF, find power, backhaul and mounting points. You get a survey report and constraints list.
DesignCoverage plans, equipment lists, integration with existing systems. You get a deployment plan and bill of materials.
Staging and factory acceptanceEverything is built and tested in our shop before it ships. You get a passed acceptance test before anything reaches the site.
InstallWe have covered more than 50 acres in a one-week install, and a venue-wide charging rollout went in over half a day.
Commissioni-ng and live supportOur engineers stay on site and watch the system under real load. You get a commissioning report and a live contact.
Handover or ongoing operationWe train your staff to run it, or we keep running it for you.

Every phase ends at a review.

The review is a working session with the engineers who did the work. It usually takes an hour. You leave it with three things:

  • What we built and tested. Hardware, code, test data and documents from the phase, all of it yours.
  • What we learned. Results, including what failed and what it means for the plan.
  • An updated estimate. The remaining cost and schedule, plus a fixed quote for the next phase.

Then the decision is yours: continue, change course, or stop with everything built so far.

What typical projects take.

Project TypeTypical DurationWhat Moves the CostFrom Our Work
Feasibility study1 to 2 weeksHow much already exists (sketches, a prototype, test data) and how many disciplines the idea touches.The first step on most of our projects, including every example on this page.
Class II medical wearable12 to 24 monthsDevice classification, whether a clear predicate exists, the number of standards tests, and the size of the clinical study.A multimodal chest-worn patch for remote monitoring, taken through FDA 510(k) clearance.
Connected product to pilot6 to 18 monthsThe number of custom boards, FCC or UL work, how much data each device sends, and how many sites are in the pilot.A building energy intelligence product: panel-mounted metering board, firmware, cloud, database, front end and anomaly detection, all built by one team.
Validation study3 to 6 monthsNumber of participants and sites, central or local IRB, and how demanding the statistical endpoint is.Cuffless blood pressure validation for a wearable device.
Data platform and AI4 to 9 monthsHow many data sources there are, how clean they are, and how many people need to use the result.The data warehouse, AI systems, harvest software and training program for Sun Pacific.
Temporary event network6 to 8 weeks of design, 1-week installAcreage, crowd density, available power and backhaul, and how long the network has to stay up.Festival and golf championship networks covering more than 50 acres, installed in one week, serving tens of thousands of users.
On-premises AI programMultiyear, in phasesIntegration with existing scanners and systems, the on-site hardware, and the acceptance test regime.Multiyear programs for a Fortune 500 defense and security integrator, including on-premises scan analysis at 20 to 30 containers per hour.

What you can expect every week.

  • A written status. What got done, what is next, what is at risk, and budget spent against plan.
  • A shared tracker. You see the same issue list and test results our engineers see.
  • Direct access. You talk to the engineers doing the work. The people who scope your project build it.
  • Cost changes quoted first. If scope changes, we price the change and you approve it before we do the work.

We can hand it over.

You own everything we make: design files, source code, test data, documentation. We organize it so another team can pick it up.

When you want your own team to run the system, we train them. We build the training into the plan, with real exercises on your own data and hardware, and we stay available after the handover.

FAQ

  • We price each phase separately. The feasibility study is a fixed price, and it ends with an estimate for the whole project and a fixed quote for the next phase.

  • You do. All designs, code, documentation and data we produce belong to you once the project is fully paid.

  • Yes. Download our mutual NDA, or send us yours.

  • Yes. Most clients start with a feasibility study. Others start with a single board, one validation study or one deployment.

  • Our own engineers and staff members. The people who scope your project are the people who build it, and you talk to them directly.

  • Yes. A feasibility study gives founders a credible architecture, cost and schedule to take to investors. We have previously worked out deals for delayed compensation or compensation through equity. We take these deals on a case-by-case basis.

  • Yes. We start by reviewing the existing design files, code and test data, and we tell you what we would keep and what we would change.

  • Yes. We have taken devices through 510(k) clearance, and we prepare Q-submissions, human factors files and clinical evidence.

  • Yes. We install, commission and support systems on site in hospitals, stadiums, festival grounds and secure facilities.

  • Yes. Training can be part of any project, and we plan it from the start.