Kevin Ferron Tech Consultancy & Digital Agency
I don’t sell hours. We agree on a result we can both check — a test suite passing, a release gate in CI, devices recovering without a truck roll — and a fixed price for it. I’m paid as each milestone is met.
Step 1
A fixed-fee Outcome Assessment. I dig into the code, the hardware or the team and come back with a written outcome, its acceptance checks and a fixed price.
Step 2
One page: the outcome, the milestones, the checks that close each one, and the fee. No timesheets, no rate card.
Step 3
30% on signing. The rest is billed milestone by milestone, each one invoiced when its acceptance check passes.
Step 4
Your team owns the result, with the tests and documentation to keep it working after I leave.
Where every engagement starts
$10,000
Fixed · 1–2 weeks
Credited in full toward the engagement if you go ahead.
Each one ends on a check, not a date on a timesheet.
A scenario-driven integration test harness that runs against your real firmware or services and gates every merge in CI.
Done when: The harness is a required CI check, your agreed critical and fault paths are covered, and a reproducing scenario is the accepted proof a bug is fixed.
Built one that replaced manual regression passes taking days to weeks. It grew to about 110 scenarios and four teams adopted it.
One fault-handling system in place of scattered error handling, with rule-based recovery so units return to service on their own.
Done when: The named fault classes clear without a technician reset, verified by scenario tests.
Designed this for DC fast-charger firmware that had been crashing and misbehaving in the field.
Claude Code skills, agent loops and verification gates installed in your own repositories and working the way your team works.
Done when: Your team ships real changes through the agent loop behind CI gates, with cycle time measured before and after.
Built and maintained the skills and agent workflow an R&D firmware team adopted.
EV charging conformance and interop
ISO 15118-20 bidirectional and dynamic control, Plug & Charge, OCPP 2.0.1, NACS or MCS, implemented or finished.
Done when: The charger passes the target conformance suite or interop session against named vehicles.
Third-party test suites on your hardware
An outside conformance suite running against your real hardware, unmodified, through EVerest, MQTT, Modbus or CAN.
Done when: The suite runs end to end on your hardware.
Delivered alone in three months; now used by major car makers.
One source of truth in a messy codebase
Duplicated logic such as limits, configuration or state pulled into one subsystem everything else queries.
Done when: The duplicates are deleted, tests are green, behaviour is unchanged.
Non-engineers who ship without an engineer
Tools that let product, design or operations change content, merchandising or configuration themselves.
Done when: The agreed change types no longer need an engineering ticket.
Did this at Zynga with a Unity level editor and at Booyah with build-pipeline hooks.
Rescue a stalled project
A troubled codebase or delivery brought back under control.
Done when: A stable release ships on the agreed date, or you have a written go/no-go with a costed plan.
Fractional CTO or team build-out
An engineering team stood up or reshaped, with a roadmap it can deliver.
Done when: The hires are made, the roadmap is set and the first milestone has shipped.
Built a 14-engineer mobile studio for EA, directed a 12-person org at Zynga, CTO at Booyah.
Zero to launched product
A web or mobile product built and put in front of real users.
Done when: It is live, with the agreed scope: accounts, payments, an API.
Built KruX42, a universal music-link product with a public API.
Every week your team spends retesting by hand, fighting fires in the field and re-arguing what “done” means is payroll burned on standing still. I fix the machine that makes your software — not just the software.
Weeks of manual retesting before every release collapse into a CI gate that runs on every merge. Your release calendar stops being a negotiation.
Replaced days-to-weeks regression passes with ~110 automated scenarios.
When the pipeline proves the work, your most expensive people go back to building. Same headcount, dramatically more shipped.
Four teams moved onto a test framework I built on my own initiative.
Every fix lands with a test that reproduces it, so the same defect never reaches a customer twice. Quality ratchets up with every release instead of eroding.
Made a reproducing scenario the standard proof a bug was fixed.
Fault handling, recovery and conformance designed in, not patched on. Fewer field failures, fewer truck rolls, fewer furious calls from customers.
Firmware for DC fast chargers deployed worldwide.
AI agents behind verification gates, tools that let product and ops serve themselves, and one source of truth where there used to be five. Leverage without the hiring bill.
Built the Claude Code agent workflow an R&D firmware team adopted.
Clear ownership, a roadmap the team believes in and a definition of done everyone signs. The meetings get shorter and the releases get bigger.
Director at Zynga, CTO at Booyah, built a 14-engineer studio for EA.
Embedded C++ and Rust firmware for DC fast chargers deployed worldwide. Director of Engineering at Zynga, CTO at Booyah, tech lead at Electronic Arts. You work directly with the engineer doing the work — no account managers, no junior bench. Full resume →
Not the focus of the practice, but proof that I ship and keep looking after what I ship. A few of them:
My own product. One universal music link that opens on whichever streaming service each listener already uses.
krux42.com↗
Video production company — commercial, documentary, and event films, taken from treatment to final grade.
42secondproductions.com↗
Author site for Olaf Kroneman, M.D. — the forthcoming novel Detroit Heroic plus two medical story collections.
drkronemanconfidential.com↗
Author site for J Ferron — Air Force Academy graduate and Vietnam pilot, now writing historical fiction.
jferronauthor.com↗
Family-owned tree care in Oakland County, Michigan. Service-area pages, local SEO, and estimate capture.
reactiontree.com↗Tell me what has to be true when we’re done — what you’re building, what’s stuck, or what needs rescuing. I read every inquiry myself and reply within 24 hours, usually with a proposal for the Outcome Assessment. Or email kcf@kevinferron.com directly.
Leave me a note - I'll get back with you within 24 hours