Services

What you can ask for

I do a technical executive's job for your business, for an hour or for months.

Get in touch for a free get-to-know-each-other call

The questions a technical executive answers

  • Can it be made reliably, at a high yield, without failing in the field?
  • Can it be delivered on time and on budget?
  • Will it keep running, and scale to thousands of devices or millions of users?
  • Will it make a profit?

Answering those before the money goes in, and then making sure the answers hold, is the job.

I've managed engineering departments, been an executive in larger companies, and run engineering businesses of my own, in electronic products and connected cloud infrastructure. Now I do that job for companies that make, outsource or run these products, and for the investors who back them.

You can use me for all of it, or just the part you need: an hour on a question, a few days on a review, or months running the work. How to engage

Nine things you can ask me for

No packages. Each is time at my published rates, starting with a free call.

  • Before you commit to a design

    A design review

    An architecture, code, infrastructure or schematic review while changes are still cheap, or a check that you are ready for certification.

    Usual length: a few days at $2,000 a day, often an hour first.

    Where I've done it: A-SAFE, which began with an assessment

    For: Makers, Engineering leaders

  • Before you place the order

    A factory or supplier check

    An on-site check of a factory, supplier or design house, anywhere, with a written report.

    Usual length: a few days, plus travel.

    Where I've done it: Two companies built in China

    For: Outsourcing

  • Before it has to scale

    A reliability review

    The devices, networks and cloud infrastructure reviewed together, with the weak points ranked.

    Usual length: a few days.

    Where I've done it: A live TV service, with almost no downtime

    For: Operators and buyers

  • Before you sign or invest

    A second opinion, or technical due diligence

    Will the product hold up in the field, can it be made at volume and cost, and can the team deliver it? A clear answer in writing, before the money goes in.

    Usual length: one hour for a second opinion, a few days to a few weeks for due diligence.

    Why I can offer this: I've run these companies myself.

    For: Investors and acquirers, Operators and buyers

  • For months

    A part-time technical executive

    Responsible for the whole of it: for example, one or two weeks a month.

    Usual length: months. One week a month is $9,000.

    Why I can offer this: the full-time roles I've held, as chief technical officer, managing director and chief executive.

    For: Makers, Investors and acquirers

  • From prototype to first product

    Getting a first product made

    Turning a working prototype into a product that can be made reliably and supported.

    Usual length: an hour or a few days first, then part-time support.

    Where I've done it: CIMA's first box, concept to production in about nine months

    For: Makers

  • Selling to Western customers

    Strategy for suppliers and factories

    Market and product strategy, specifications, audits and certification planning, customer relationships and setting up engineering teams.

    Usual length: weeks to months.

    Where I've done it: A new supplier for DirecTV

    For: Suppliers and factories

  • After a failure

    An investigation and a written report

    When electronic products, outsourced manufacturing or connected services fail, the dispute often turns on whether the design, the factory, the firmware or the operator was at fault. I can investigate what went wrong and set it out clearly in a report for lawyers and insurers.

    Usual length: days to weeks.

    Why I can offer this: I've spent a career preventing these failures.

    For: Spin-outs and product disputes

  • A piece of engineering

    Done hands-on

    For smaller jobs, or when it's the quickest way to get something right, I do the work myself: system architecture, embedded, gateway and back-end software, and cloud infrastructure on Amazon Web Services.

    Usual length: weeks to months.

    Where I've done it: Beyond the role

    For: Engineering leaders

From a free call to a month

  1. First callFreeTo get to know each other No obligation, at a time that suits you.
  2. One hour$300A decision talked through Or a second opinion before you invest.
  3. A few days$2,000 a dayA review, in writing Of a design, a factory or a company.
  4. A few weeks$9,000 a weekThe plan and the architecture And the choice of suppliers.
  5. A few months$34,000 a monthBuilding it Or keeping it on track.
  6. OngoingBy the day or weekPart-time technical executive Or technical advisor.

You pay for time, at published rates. The longer you engage me, the less each hour costs. Rates and terms

At any stage

  • An ideaBefore the money goes in: can it be made, delivered and run at a profit?
  • Part way throughBefore the next commitment: the factory order, the launch or the next funding round.
  • Already runningBefore it has to scale, or cost less to run.
Antony Haines

Want those questions answered before you commit?

Tell me what you're planning and I'll tell you where I see the risks.

The first call is free, with no obligation: it's for us to get to know each other. Send me a message, I'll get back to you, and we'll find a time that suits you, wherever you are.

Get in touch for a free get-to-know-each-other call

Rates and terms

Or reach me directly

Get in touch