Enterprise evaluation framework
Most wireless-energy pilots end in a slide deck. Not a decision.
The 13-week framework we use to scope, run and judge an enterprise proof-of-concept — including the questions you should ask any vendor, us included.
Free. No sales call. No demo booking.
- Patent estate anchored to October 2017 priority
- Granted coverage across 21 jurisdictions
- Commercialization partner: Apex Financial Partners
- Published milestone track record
Wireless energy is easy to demo and hard to evaluate
Demos prove nothing.
A controlled demonstration tells you a device received power. It tells you nothing about efficiency, thermal behaviour, range, safety or whether it survives your environment.
Power alone is not the product.
In an audited enterprise environment, energy delivery has to be authenticated, authorised, measured and logged like any other critical infrastructure. Most evaluations never test that layer.
Pilots drift.
Without defined success criteria and evidence requirements agreed up front, a pilot becomes a science project that ends in a slide deck instead of a decision.
Three of the questions in the framework
If a vendor can't answer these, the pilot will not survive procurement.
01
“Which of your published results are measured, and which are modelled? Show me the test report for each.”
Most wireless-power claims blend the two. A vendor who can separate them on the spot has an engineering discipline you can audit. One who can't has a marketing department.
02
“When a device requests power, what exactly authenticates it — and what happens if authentication fails mid-session?”
This is the question that separates a demo from infrastructure. If the answer is “it just receives power,” there is no security model to review, and your security team will end the evaluation for you.
03
“Show me a signed telemetry record for a single energy session, and tell me who can and cannot alter it.”
If energy is going to be metered, billed or audited, the record has to be defensible to someone who wasn't in the room. Ask to see one.
There are twenty-two more in the framework. Read all 25 questions and the evidence standard — free, no form.
Why I wrote this
I spent three years at Ingram Micro scaling mission-critical e-commerce infrastructure from a single server to a distributed, load-balanced architecture running across 32 countries, then consulted for Microsoft on application clustering and web-scale deployment. For the last decade I've been building wireless energy systems.
I've sat through a lot of infrastructure evaluations, and the wireless-power ones fail the same way almost every time: an impressive demonstration, no agreed success criteria, no evidence requirements, and a pilot that quietly becomes a science project. Nobody is dishonest. The evaluation was just never designed to produce a decision.
So this is the framework I would want if I were on your side of the table. It includes the questions that are hardest for us to answer, because those are the ones worth asking.
Robert Smith
Founder & Chief Executive Officer, ATLAS Power Networks
What the framework gives you
- A 13-week structure with defined phases, owners and decision gates
- Success criteria you set before the pilot starts, not after
- The evidence requirements that make a result defensible internally
- A vendor question set covering authentication, telemetry, metering and audit
- The distinction between measured results, modelled performance, design objectives and future plans — and how to make a vendor state which is which
- A commercial conversion path, so a successful pilot has somewhere to go
Weeks 1–2
Scope and success criteria
Define what the pilot must prove, who owns each outcome, and what result ends the evaluation either way.
Weeks 3–4
Environment and constraints assessment
Power, thermal, RF, network, safety and security review of the actual site.
Weeks 5–8
Integration and instrumented testing
Deploy, instrument, and collect measured results against the criteria set in week 1.
Weeks 9–10
Evidence package
Assemble results in a form that survives internal review, clearly labelled measured, modelled, objective or plan.
Weeks 11–12
Review against criteria
Compare evidence to the week-one criteria. No moving the criteria.
Week 13
Decision and conversion path
Proceed, stop, or extend, with commercial terms already defined.
Built for
- Enterprise operators evaluating wireless power for the first time
- Industrial IoT and sensor deployments where cabling is the constraint
- Robotics and autonomous systems needing power without docking
- Logistics and edge sites where conventional connectivity is limited
- Government programmes with audit and evidence requirements
- OEMs assessing integration into shipped products
Get the framework
Enter your details and the framework arrives immediately. We'll send occasional updates on the enterprise programme — one email a month at most, unsubscribe in one click.
Already past the evaluation stage?
If you've done this work and want to talk about a paid pilot with defined scope, success criteria and a commercial conversion path, say so directly and we'll set up a technical conversation.
Request a pilot conversation