K Malakuti

Executive by trade. Engineer by training. Inventor by habit.

A fractional technology executive who still builds.

I’ve owned $1B+ product portfolios and have hands-on experience with AI going back to 2008. Through Aras Peak Group, I join your leadership team at the intensity you need, priced on outcomes.

Book an intro callSee the work

Principles

  • Outcomes, not hours.

    Priced on the results we agree on. A partner, not a vendor.

  • The right answer, even if it isn’t me.

    If someone else is the better fit, I’ll say so, and help you find them.

  • Owned the number.

    $1B+ product portfolios, mergers and acquisitions, multinational teams.

  • In the room where it’s decided.

    Board, executive team or architecture review: I sit with the people who make your business run, and make their calls sharper.

  • Chosen, not chased.

    I take on a few engagements a year, the ones where I can move the number.

The Record

Outcomes, with the years they took.

  • 2008–2010

    Computer-vision thesis, a co-founded research lab, and a paper at ICPR.

    MASc, Electrical Engineering, University of Victoria (Applied Computer Vision Algorithms lab). Before that, degrees in electrical and nuclear engineering.

  • 2010–2015

    Built a SCADA-based lighting-control interface that became a core product.

    Douglas Lighting Controls, later acquired by Panasonic. Joined as an application engineer.

  • 2011

    Patented occupancy sensors that learn which sounds mean people are present, then launched the sensor line.

    Douglas Lighting Controls. Filed 2011, granted 2014. Then led the launch of a patented occupancy-sensor line.

  • 2015–2020

    OEM and ODM partnerships for the hardware line: +5 points of gross margin.

    Video infrastructure at Avigilon, part of Motorola Solutions from 2018.

  • 2019–2020

    Video infrastructure grew 20%+ a year, faster than any other business unit.

    Avigilon, Motorola Solutions.

  • 2020–2021

    Led the industry's first AI NVR: +30% incremental revenue.

    A network video recorder with the AI built in. Director of Product Management, AI Platforms, Avigilon.

  • 2021

    Top Invention of the Year 2021 at Motorola Solutions, for the patent on access control that learns to predict intent to enter.

    Avigilon, Motorola Solutions. Filed December 2020, granted October 2021.

  • 2021–2022

    Turned four brands' video roadmaps into one.

    Johnson Controls: Exacqvision, American Dynamics, Illustra and Tyco AI.

  • 2022–2025

    Grew revenue at twice the market rate, every year.

    Video and access control, Avigilon (Motorola Solutions). Recruited back by senior leadership in 2022.

  • 2022–2023

    Portfolio revenue +24% in a year; gross margin +3 points from pruning the line.

    Revenue growth came from integrations with government and public-safety systems.

  • 2022–2025

    Product lead on several acquisitions, from diligence to fold-in and team integration.

    Motorola Solutions.

  • 2023–2025

    Led product for a 300-person development organization, with 26 direct reports.

    Senior Director of Product Management, video and access control. Avigilon, Motorola Solutions.

  • 2025

    Recurring revenue from the installed base reached 20% of software revenue.

    Simpler licensing the same year: net-new customers +30% in the first half.

  • 2025

    Conceived and led the industry's first VLM-based Visual Alerts.

    Vision-language models watching live video for situations described in plain language. Avigilon, Motorola Solutions.

  • 2025–now

    Founded Aras Peak Group: fractional executive leadership, and enterprise-grade engineering from silicon to cloud.

    Independent since October 2025. The firm offers fractional executive and board advisory, and builds its products with Conductor, an AI software delivery lifecycle with expert human judgment at the gates.

AI since 2008

The thread through 18 years: computer-vision research, then patents, then shipped products, at the edge and in the cloud.

  1. 2008Master's thesis: computer vision reads sleep from a pressure-sensing bed sheetComputer visionResearch
  2. 2010ICPR paper: telling breathing, apnea and movement apart with computer visionPattern recognition · computer visionResearch
  3. 2011Patent: occupancy sensors that learn which sounds mean people are present (granted 2014)On-device audio classification · edge AIPatent
  4. 2020Avigilon (Motorola Solutions): led the industry's first AI NVREdge video analyticsRole
  5. 2020Patent: access control that learns to predict intent to enter (Motorola Solutions’ Top Invention of the Year 2021)Machine learning · intent predictionPatent
  6. 2021Patent application: teaching video analytics by example with clustering and active learningActive learning · video analyticsPatent
  7. 2025Avigilon (Motorola Solutions): conceived and led the industry's first VLM-based Visual AlertsVision-language models · generative AIRole
  8. 2026Oshkidar: radar with an on-device ML modelOn-device radar classificationProduct
  9. 2026Stuword: compliance answers with verified citations (early access)Retrieval with verified citationsProduct
  10. 2026Conductor: an AI software delivery lifecycle with expert judgment at the gatesAI SDLC · agentic deliveryProduct

Inventions

Six patent families, four peer-reviewed papers and three theses.

Patents

Papers and theses

  • 2004

    A wearable ultrasonic step-distance meter with spoken feedback for blind pedestrians

    A device worn on the shoe measures the distance between the feet with ultrasound at every step, adds up the distance travelled and reads it aloud to a blind walker.

    Azad University (BASc, Electrical Engineering) · English title; the thesis is not in English

  • 2006

    Fusing anatomical and functional medical images: CT and MRI with PET and SPECT, reconstructed in 3D

    Software that overlays function from PET or SPECT on the sharper anatomy of CT or MRI and reconstructs the result in 3D, so it can be sliced and viewed from any angle.

    Shahid Beheshti University (MSc, Nuclear Engineering) · English title; the thesis is not in English

  • 2008

    Interdisciplinary Project-Based Learning in Ergonomics for Software Engineers: A Case Study

    An ergonomics course project in which software-engineering students found where older users made errors with a software tool, then redesigned it.

    IEEE · 3rd International Conference on Software Engineering Advances (ICSEA 2008) · 10.1109/ICSEA.2008.70

  • 2008

    EasyDSP: Problem-Based Learning in Digital Signal Processing

    EasyDSP, a custom framework that let university signal-processing students pose and solve their own multimedia problems alongside lectures.

    Canadian Engineering Education Association (CEEA 2008) · 10.24908/pceea.v0i0.3751

  • 2008

    Towards an intelligent bed sensor: Non-intrusive monitoring of sleep disturbances via computer vision techniques

    Computer vision

    A bed sheet with 144 pressure sensors whose readings are treated as images, so computer-vision techniques can detect breathing, apnea and movement at home.

    University of Victoria (MASc, Electrical Engineering) · hdl:1828/1297

  • 2009

    Work in progress: Problem-based learning in digital signal processing

    Early results from adding student-defined, problem-based projects to a lecture-based signal-processing course, so the math meets real problems.

    IEEE · 39th Frontiers in Education Conference (FIE 2009) · 10.1109/FIE.2009.5350718

  • 2010

    Towards an Intelligent Bed Sensor: Non-intrusive Monitoring of Sleep Irregularities with Computer Vision Techniques

    Pattern recognition · computer vision

    Turns bed-pressure readings into images, then uses computer vision and pattern recognition to tell normal breathing, sleep apnea and body movement apart.

    IEEE · 20th International Conference on Pattern Recognition (ICPR 2010) · 10.1109/ICPR.2010.974

Six months, one question.

I’m a product executive: fifteen years in enterprise product, most recently at two Fortune 500 companies. I left with a question I wanted to answer with my own hands: if you started a software development process from scratch today, with AI, what would it look like? I spent six months building one. This is what I came up with, and the products it was tested on.

What I came up with

AI does the legwork. Expert judgment decides.

Fifteen years of enterprise product judgment, most recently at two Fortune 500 companies, built into an AI software delivery lifecycle.

40%
of model calls routed to a lower-cost tier; the most capable model is kept for planning, blind tests and review
1 in 8
shipped features stopped at a one-way door for a signed human decision
3
adversarial critic rounds (median) on each one-way-door design, before any code is written
10+
automated quality-gate runs per shipped feature (median): unit, end-to-end, dependency-age and scope checks

Anyone can point AI agents at a codebase. The difference is when a person decides. Conductor, the process I arrived at, works like an engineering team that knows when to escalate. Routine implementation runs on a fast, lower-cost model; planning, blind test-writing and review run on the most capable one. When an implementation fails its checks twice, the final attempt moves up to the stronger model. When the builder meets a question it shouldn’t settle alone, it stops and asks. And every decision that is hard to reverse, such as a database schema, an authentication design, pricing or a deploy target, waits for a senior human. Expert time goes where it changes the outcome, and delivery stays cost-effective, predictable and high quality.

Nothing advances on a model’s say-so. Gates are exit codes, tests are written blind by a model that never sees the implementation, and a reviewer’s approval is bound to the exact commit it read. Each one-way door is red-teamed by adversarial critics, and the work does not start until the decision is signed; other work keeps moving meanwhile. The questions asked at those doors come from shipping enterprise products at Motorola Solutions, Johnson Controls and Panasonic.

Every run leaves a receipt in a ledger: the models used, tokens, cost, time, and the commit that was reviewed and merged. Across 118 features shipped in three products, that ledger is how I know the process works.

The products were the test. The process is the result.

Conductor, the system behind it

Agents do the legworkA person decides
  1. The brief

    A person decides what to build and what done means.

  2. Plan

    Agents break the work into slices and plan each one.

  3. One-way doors

    Anything hard to reverse, such as a schema, a deploy target or a credential, is red-teamed, then waits for a signed decision.

  4. Build

    Agents write the code against the plan.

  5. Test

    Automated gates decide by exit code; blind tests come from a model that never saw the code.

  6. Review

    Approval is bound to the exact commit that was read.

  7. Merge

    Refused if anything changed after review.

  8. The read

    A person reads the ledger, not a transcript: models, cost, time and the commit that shipped.

What six months taught me

The trade between cost, speed and quality is as old as software. What AI changes is where the levers are. Six months of ledgers, checked against fifteen years of late decisions, found them in three places, none of them obvious, and each one a judgment call.

A triangle with Quality at the top, Cost at the bottom left and Speed at the bottom right. Inside it, three shapes: a team of humans is a thin spike toward quality; agents alone are a flat wedge along cost and speed; the method is a large triangle that reaches most of the way to all three.

A team of senior humans reaches the quality corner, at a cost and a pace few projects can afford. Agents on their own are cheap and fast, and can’t be trusted with the outcome. The method’s shape is the judgment: it gives up the least on all three. Each lever below protects one corner.

  • Separate the hands.

    Design the graph, not the pipeline. The hand that checks the work gets the same brief as the hand that builds it, and never the build itself. Nobody grades their own work. That is what makes an agent’s output trustworthy, and trust is what lets it run unattended.

    A small graph of roles: a brief fans out to two hands, build and check, separated by a wall marked no shared view; they meet only at the result, which goes to a person who decides. Caption inside: a graph of roles, not a line of steps.
    Two hands, one brief. They meet only at the result, and a person decides.
  • Size the loops.

    Every retry costs time; every escalation costs more. A loop that asks too early makes a person the bottleneck; one that runs too deep spends a night going in circles. The depth sits where iterating starts to cost more than asking. Finding it is judgment, not configuration.

    Three loops drawn as rows of attempts. Too shallow: one attempt, then a person. Sized: a few attempts, the last one escalated, then a person. Too deep: attempt after attempt fading to the right, never asking.
    Shallow, sized, deep: the loop asks when iterating stops paying.
  • Route by stage.

    Not every step deserves the most capable model, and the steps that do are not the obvious ones. Spend expensive judgment, human or machine, where it changes the outcome, and let the rest run cheap. Model routing is a budgeting decision, not an engineering one.

Where the hands separate, how deep the loops run, where the expensive judgment goes: that balance is what I bring to your table.

The products it was tested on

None of these is a minimum viable product. Each was picked for a different layer, silicon to cloud, then taken as far as the engineering would go and held to the standard an enterprise would demand: security, architecture, performance, observability, quality. A sprinkler doesn’t need signed over-the-air updates, a file system that never loses a day, or a timeline that streams over a weak Wi-Fi link. It has them, because the question was never the sprinkler. The question was whether one process could reach that depth, in months, at a cost a small company can carry. Ten projects later, the answer is below, and one of them, esp32-seed, is that standard handed to anyone who wants it.

  1. Silicon

    Firmware, radios, sensors, and AI models small enough to run on the device.

    Oshkidar

    Deployed2026

    Real-time AI on a $2 microcontroller: radar classification that flushes only for the cat.

    62
    engineered radar features, each documented with the physics of why it separates a cat from a ghost
    1,500
    gradient-boosted trees classify every window as cat, person, refill water, ghost or empty
    1 Hz
    real-time inference on the chip, over a sliding 8-second window of 10 Hz radar frames
    343 KB
    of flash holds the whole model; a Bayesian tracker and a state machine decide when to flush
    sprinklerd

    Deployed2026

    Drop-in, set-and-forget sprinkler controller: per-zone soil-water modeling and weather forecasts, no subscription.

    0
    cloud services required: schedules, rain and freeze holds, and the water-balance model all run on the chip
    2,115
    lines of dashboard web app, served straight from the microcontroller
    ECDSA P-256
    signed firmware updates: an image with a bad signature is rejected on the device
    AP + STA
    Wi-Fi modes with captive-portal setup; three quick power cycles open a recovery access point, no tools needed
    esp32-seed

    Released2026

    ESP32 firmware framework: signed updates, Wi-Fi, storage, time sync and web admin, built in.

    ECDSA P-256
    signed over-the-air updates, verified while they stream in; each device generates its own secrets on first boot
    AP + STA
    Wi-Fi with captive-portal setup, and a recovery access point after three quick power cycles
    LittleFS + NTP
    a filesystem with daily audit logs, and network time sync with a fallback
    Web admin
    built in: dashboard, settings and firmware updates, on ESP32, S3, C3 and C6 chips. Add your application on top.
    iPhone keep-alive

    Deployed

    Keeps an iPhone's personal hotspot from shutting off by sending it periodic requests.

    Periodic
    requests keep the iPhone's hotspot awake, so it doesn't shut down its Wi-Fi
    Ancestor
    its Wi-Fi, access-point, update and file-handling code was lifted unchanged into Oshkidar, and from there into esp32-seed
  2. Edge and cloud

    Distributed, cloud-hybrid systems: devices in the field, heavy lifting in the cloud.

    IP Timelapse

    Deployed2026

    Cloud-hybrid timelapse SaaS for distributed organizations: edge workers capture, the cloud renders.

    0
    inbound ports opened on a site's network: edge workers dial out to the cloud core
    Org → site → edge
    every site, edge credential and stored frame belongs to an organization; an upload that doesn't match its edge's own site is refused and logged
    10 s
    edge heartbeat with its camera list, capture-worker health and upload backlog; the cloud flags stale cameras, low disk and upload lag
    172 of 172
    frames delivered after a storage outage test: the edge buffers in a durable queue, with no loss and no duplicates
    SetSlice

    Early access2026

    Desktop software that turns one long recording into separate, named songs, even when there's no gap between them.

    ~5.5 KB
    sent per song lookup: a fingerprint computed on your computer, never the audio. About 300 KB per hour of recording
    0.2 s
    median gap between a cut and the song start its fingerprints point to; all 10 cuts in a 48-minute test within 1.2 s
    ~3 min
    to name every song in a 48-minute recording; the local signal analysis takes 9 seconds of that
    25 hours
    of song identification in the one-time early-access price; splitting and MP3 export run on your computer
  3. Software as a service

    Multi-tenant SaaS products with real users and automated releases.

    DinQueue

    Released2026

    League-night SaaS for pickleball: deterministic matchmaking, private preferences, live court boards.

    950+
    automated tests: property-based engine tests, database-security tests and end-to-end browser tests
    Invite links
    take a player straight into a league on signup; players without an account can still be checked in and seated
    2 s
    refresh on the captain's board and players' phones; the gym-TV wallboard shows courts and the queue
    3
    roles with their own views (captain, co-captain, player), plus anonymous notes to captains, sealed at the database
    SinceWe

    Released2026

    Household SaaS, installable from the browser, that answers: how long has it been?

    0
    signup steps: the first visit starts an anonymous account that later upgrades in place to a passkey account
    Passkeys
    sign-in with WebAuthn and no passwords, with an email link as the fallback
    PWA
    installable progressive web app with an offline outbox, one codebase kept ready for a native wrapper
    Real-time
    household sync: local-first on each device, idempotent writes that can never duplicate an entry
  4. Applied AI

    AI that people can check, not just trust.

    Stuword

    Early access2026

    AI compliance assistant: every citation verified, word for word, against approved sources.

    0
    unverified citations shown: a citation that fails the deterministic check is stripped and logged
    Clause-level
    citations anchored to a section, clause or control ID in a human-approved document version
    NIST SP 800-171
    and CMMC: the first compliance domain, with a company's own policies alongside the standard
    Every answer
    leaves an audit record: who asked, what was answered, and from which document version

I’m not here for the engagement. I’m here for the outcome.

Fractional leadership is billion-dollar judgment at the intensity your problem actually needs.

Engagements run through Aras Peak Group: my judgment and leadership, plus senior people from my network, many from the Fortune 500 companies I've worked for, brought in when the problem needs deeper engineering, finance or investor relationships.

Ways to work together

  1. Discovery

    A short, flat-fee engagement. You get my honest read, including whether you need me at all, plus a scope and a compensation model tied to the outcomes we agree on.

  2. A seat at your table

    Board, executive team, or both. You set the intensity; my compensation follows the metrics we agreed on.

  3. In the room

    With your leadership and your best people: strategy, operations, product, engineering and go-to-market.

Book an intro callSave contactLinkedIn

Or leave a note