Skip to content
Cenotian
Watercolor study of robot arms over a production line

USA or Europe

Lead Automation Value Engineering (Enterprise)

You turn enterprise automation ambitions into funded programs, supplier decisions and repeatable deployments - and build the practice that delivers them.

You build our vendor-neutral Enterprise Automation Programs and Value Engineering practice from anchor accounts into a profitable business. You win engagements, lead the delivery pod and personally author business cases, program architectures and sourcing packages. You own the offer, commercial model, method, recommendations, partners, outcomes and economics.

Context

Cenotian provides capital and capabilities for physical automation across the US and Europe. Enterprises need independent methods to compare opportunities, structure supplier-executable work, prove performance and carry decisions through procurement and rollout.

Position overview

Engagements are modular: start with an operating problem, automation ambition, supplier proposal, sourcing decision or stalled program, not a fixed sequence. Earn revenue independently while connecting suitable opportunities to Cenotian's qualification, compliance and capital capabilities without compromising advice. Frequent travel to factories, workshops, supplier sites and client decision forums.

Reports to:
Head of Special Missions (Launch phase)
Location:
USA or Europe

Key responsibilities

  1. 01

    Diagnose the mandate and build the capital case

    • Establish the baseline, target outcome, scope, assumptions, constraints, dependencies and decision evidence.
    • Align executive sponsors, economic buyers, technical authorities, plant teams, procurement, finance, IT, operational technology, cybersecurity, safety and legal. Set decision rights, approval gates and escalation paths.
    • Build business cases covering total deployment and lifecycle cost, operating benefit, ramp, downside, payback, cash requirements and financing alternatives, using the enterprise's hurdle rates and approval artifacts.
    • Rank opportunities across sites and business units consistently. Separate immediate deployments from process stabilization, controls, data, cybersecurity, layout or workforce preparation. Recommend proceed, redesign, defer or stop, with traceable evidence and conditions.
  2. 02

    Turn outcomes into jobs and work packages

    • Decompose operating outcomes into functional jobs: sensing, inspection, handling, movement, manipulation, control, safety, security, data exchange and operator interaction. Define inputs, outputs, performance, interfaces, dependencies, failure modes and acceptance criteria.
    • Group jobs into market-procurable packages with clear boundaries, supplier responsibilities, sequencing and acceptance logic. Decide what belongs with a lead integrator, specialist, OEM or coordinated providers at plant, regional or enterprise level.
    • Compare concepts, automation depth, architectures, bills of materials, service and implementation. Expose hidden scope and dependencies; preserve later-package feasibility.
    • Set enterprise standards, site assumptions, permissible variations and deviation governance. Protect future competition through open interfaces, data ownership, infrastructure capacity, documentation and access rights. Trace each job to its package, supplier response, test and acceptance decision.
  3. 03

    Build a qualified supplier field

    • Maintain capability maps of integrators, OEMs, specialists, simulation providers and regional experts. Filter the broad market into a credible bidder field by geography, capability, financial capacity and delivery evidence.
    • Assess application fit, architecture, installed base, cybersecurity, data, service coverage, operating environment, contracting maturity and execution risk through references, project histories, management interviews and site visits.
    • Set evidence, safety, security, service and performance standards. Update scorecards from proposals, delivery, defects, acceptance evidence, support and realized outcomes.
    • Match suppliers to the work, not commercial preference. Enforce rules for conflicts, referral economics, disclosure and data use; keep advisory recommendations separate from technical qualification and financing decisions.
  4. 04

    Author and run enterprise sourcing

    • Produce issue-ready RFI, RFP and RFQ packages: functional requirements, scope and interface specifications, bidder instructions, pricing and commercial schedules, evaluation criteria, acceptance frameworks and response templates.
    • Require requirement-level pricing that isolates options, external integrations and deferred scope without repricing the package. Separate proof-of-concept from rollout pricing and expose site and program assumptions.
    • Manage introductions, consolidated questions, clarification, site visits, submissions, interviews and evaluation. Normalize technical, commercial, lifecycle, contractual and delivery responses.
    • Close internal dependencies with procurement, legal, finance, IT, operational technology, cybersecurity, safety, engineering and plants. Surface exclusions, hidden costs, architecture conflicts, data restrictions and contract risks. Recommend an award with a complete evidence-based rationale; the client decides.
  5. 05

    Define proof, acceptance and rollout

    • Separate installation, commissioning, testing, demonstration and proof of functionality. Define factory or bench acceptance, site acceptance, requirement-level tests, defect registers, closure evidence and sign-off.
    • Specify safety-critical evidence: standards, failure-mode analysis, safe degradation, certification and live fault demonstrations. Require detailed and as-built designs, inventories, interface records, credentials handover, training, manuals, spares and support proposals.
    • Set the conditions for accepting the first site and committing to rollout. Convert accepted proof into a standard design, rollout package, cost model, deployment sequence and controlled site-variation process.
    • Support implementation governance, change control, supplier coordination, acceptance oversight, defect closure and value assurance. Qualified suppliers retain detailed engineering, certification, integration, installation, commissioning and service responsibility.
  6. 06

    Win engagements and build the practice

    • Launch tightly scoped, paid entry offers that produce a decision or executable next step. Build target accounts and account plans across enterprise manufacturers and multi-site industrial groups in selected regions and verticals.
    • Win anchor mandates through outreach, Cenotian relationships, strategic partners, integrators, OEMs and industry networks. Lead discovery and delivery personally; expand successful work into references, repeat engagements, multi-site programs and qualified deployment or financing opportunities.
    • Turn engagements into reusable diagnostics, economic models, job taxonomies, package architectures, supplier data, sourcing materials, evaluation models, acceptance protocols, benchmarks and rollout playbooks.
    • Control document issuance through traceability, dependency closure, versioning, quality review, client approval and release checklists. Use code, simulation and AI to reduce work without delegating judgment or losing evidence lineage; distinguish site work from remotely captured evidence.
    • Own pipeline, conversion, revenue, utilization, delivery cost, gross margin and account expansion. Recruit the initial delivery pod, define core versus partner capabilities and expand only when demand and unit economics justify it. Build quality and account governance that scales without founder dependence.

You'll know it's working when

Sponsors pay for decisions.

Issue-ready packages arrive faster with traceable requirements, closed dependencies, client approval and comparable bids.

Weak opportunities stop; strong ones become accepted deployments and controlled rollouts.

Clients trust recommendations to redesign, delay or do nothing.

Repeat revenue and margin become predictable without losing quality; every engagement improves the evidence.

Candidate profile

What we require

Nice to have

Background paths

  • 01MBB Principal who sold and delivered industrial transformation

  • 02Selling engineer who broke into enterprise

  • 03Hyper-automated operator who built the rollout machine

Organizational context

You work with the CEO, Special Missions, Commercial, Client Service Delivery, SMG Principals, Technical Qualification Services, Finance and Underwriting, Data and Platform teams, and specialist delivery partners.

Apply for this role

Up to 2000 characters.