Motivo Engineering:
a function built from zero

The situation

Motivo Engineering is a product development firm that takes hard engineering problems — robotics, aerospace, maritime, mobility — from concept to production. The work was excellent and the pipeline was personal: deals arrived through the founders' networks and referrals. There was no marketing function, no BD system, and no instrumentation. Growth was capped at the number of rooms leadership could be in.

What I found

The classic services-firm pattern. Positioning that described capabilities ("we do mechanical, electrical, software") instead of outcomes a specific buyer recognizes. No account list — every conversation was inbound luck. Conference attendance treated as presence, not pipeline: booth, badge scans, silence. And no CRM discipline, which meant no institutional memory of who mattered and why.

What I built

• Account-based plans across four verticals. Robotics, aerospace, maritime and mobility — each with named target companies and company-specific engagement plans, not a generic sequence with a first-name token.
• A signal-monitoring system on n8n and Capsule. Automated detection of account triggers — funding, hiring, product news, conference activity — feeding a prioritized outbound queue, so BD time went to accounts showing intent instead of a cold alphabetical list.
• Conference programs run as demand programs. Robotics Summit, ACT Expo, VFS Forum and SEMA — target accounts identified and contacted before the show, meetings booked in advance, structured follow-up after. The booth became the middle of a sequence, not the whole play.
• The reporting layer. Pipeline influence tracked in the CRM, so the function could be judged on opportunities, not activity.

What changed

The firm went from founder-sourced deals to a systematic motion: a named-account universe, a weekly queue ranked by signal, and a conference circuit that produced booked meetings instead of scanned badges. Pipeline figures are confidential — what I can show you is the system, and the system is the point: it ran on documented workflows a successor could operate, which is the standard every engagement here is built to.

What I'd do differently

Start the signal monitoring in month one, not after the account plans — the triggers turned out to be the best input into account selection, and I built them in the wrong order. And I'd put a content engine behind the BD motion earlier: engineers respond to outbound dramatically better when there's a technical artifact attached, and we were producing those artifacts by hand, late.