For robotics and automation integrators

Catch the missed requirement before FAT

Haymaker writes down each requirement as the customer says it on the call, so a gap shows up at kickoff.

01 · Capture

Gather requirements with every conversation

Haymaker listens in on the customer call and writes down each requirement as it is said, with the exact quote, the speaker and the time. Your team can review every line.

  • Exact quote
  • Who said it
  • When

A kickoff call with a live transcript. The project manager asks about throughput and the plant lead says "We need 60 parts a minute." When the call ends, Haymaker reads it and writes requirement REQ-014, throughput of 60 parts a minute, with the exact quote, the speaker, the time and the call.

03 · Flag

Contradictions surface before the build

When a document disagrees with what the customer said, Haymaker flags the requirement and puts both sources side by side.

  • Flagged on arrival
  • Both sources shown

Requirement REQ-014, throughput, is flagged as a conflict. The customer's plant lead said "We need 60 parts a minute" on the call at 14:32, and the safety review PDF limits the cell speed to 45 parts a minute. Both sources stay attached to the requirement.

04 · Record

One record from kickoff to handover

The requirements and every source behind them stay with the project, so the team stops rebuilding what happened from memory.

  • Full history
  • Every source attached

A ten-month project timeline, January to October. A conflict is caught in February, well before FAT in September. Below the timeline, a list of confirmed requirements scrolls up and fades out, longer than fits on screen.

One requirement, two projects

Week 1Call

Said once

"We'll need an interlock on the guard door."

Without Haymaker

  1. Week 3Kickoff

    Not in the spec

  2. Week 10Design

    Built without it

  3. Week 22FAT

    Rework at FAT

    "Where's the interlock?"

With Haymaker

  1. Week 3Kickoff

    Caught at kickoff

    Missing from the spec. Added.

  2. Week 10Design

    Designed in

  3. Week 22FAT

    Passes FAT

    The interlock is there.

Requirements decide the project

47% of unsuccessful projects miss their goals because of inaccurate requirements.

PMI, 2014

58% vs 21% of projects perform well, by strength of requirements practices.

NDIA and Carnegie Mellon, 2012

It works inside the tools you already run

Haymaker updates Jira and links each requirement to its pages, emails and drawings. Your team asks from the tools they already use. Your files stay put.

See the integrations

Built for the people who run the project

Project managers

Bill every change

Each new request is checked against the scope the customer confirmed.

Confirmed scope

New requestWeek 12

Add a third infeed laneNot in scopeChange order

Engineers

Know where every number came from

Each requirement links to the call, email or study behind it. Anything said only once is flagged.

Requirements, with source

Sales

Quote with projects like it

Similar past projects come up with what was asked and how they tested, ready to show the customer.

Past projects like this one

Bring a project where something showed up late

Tell us what happened and we show you how Haymaker would have recorded it.