A Cirql tool · for industrial & manufacturing teams

See how your plant actually runs.

We ask every person in your company — operator to COO — fifteen minutes of questions on their phone. As fast as you want: one day end-to-end when your team is told to finish it by 5pm. You get a ranked list of things to fix, with direct quotes and hour-by-hour costs. No consultants. No meetings. $2,500 · 4 assessments over 12 months — each one tracking what changed since the last.

4 runs / year · phone-friendly · one-day turnaround · no consultants
$2,500 credited toward any Cirql build within 60 days of any run. Treat the campaign as pre-paid diagnostic for your implementation.
What you're seeing · three people on the floor all report the same bottleneck — waiting on one manager's approval. Their supervisor and plant manager confirm it when asked. Two tools (the ERP and a paper approval form) are entangled in it. That pattern becomes one finding in the report.
Field report · approval bottleneckLive
§ The interview

Real questions. In plain English. On their phone.

Fifteen minutes on any phone — no app, no login. Voice or type. Adapts as they answer.

9:42
Cirql · interview
6 / 12
Walk me through a typical Tuesday on Line 2. What takes up the biggest block of your shift?
Changeovers, mostly. And the morning huddle bleeds into an hour of chasing paperwork. I don't actually start running parts until about 9:30.
That “chasing paperwork” — is that you filling out forms, or waiting on the scheduler to release the work order?
Both. Mostly waiting on Quality to sign off on the last lot. I call, I wait, I walk back and forth.
Type your answer…
Line 2 operator · between runs
§ why this exists

A note from the team.

Teams kept telling us the same thing: we want to build with AI, but we don't know where to start. Every workflow looks like a candidate, every tool pitches itself as the answer, and the safest move ends up being no move at all.

So we built this. Cirql is a fifteen-minute conversation with everyone in your org — operators, supervisors, leadership — that surfaces where work actually breaks, what's repetitive, and which tools are fighting your people. You get a ranked map of the opportunities worth automating and the ones that aren't.

Less invasive than a consultant, more honest than a survey, faster than process mining. Insight and direction, before you commit to building anything.

— The Cirql team

§ 01 / The problem

You know something's wrong. You can't name it.
Your ERP won't tell you. Your people will.

Plant managers feel the drag. Operators live with it. Nobody asks them in a way that surfaces the pattern. We do — every role, every shift, every site — and show you what's actually there.

A — Bottlenecks

One station holds up the whole line.

One supervisor signs every release. One forklift everyone waits on. One inspection step your plant runs through twice. We find the node where your throughput breaks.

B — Tool & spreadsheet sprawl

An ERP, a MES, and eleven spreadsheets.

Everyone uses the one screen they know. The real source of truth is a workbook on someone's laptop. We map every system and every overlap.

C — Repetition

The same job, every shift, every day.

Twenty minutes re-entering a work order. Times forty operators. Times three shifts. Times every day. We flag the ones worth automating.

§ 02 / How it works

Four steps, from roster to report.

No IT project. No seat licenses. No integration into your ERP. Ten minutes to launch. The rest of it is as fast as your team's phones — one day end-to-end is common when leadership says “by 5pm today”, two weeks is the outside case.

i.

Roster.

Upload your people — operators, supervisors, schedulers, quality, maintenance, front office, leadership. Tag site, shift, and role.

CSV · 30 sec
ii.

Invite.

Each person gets a unique link by text or email. No logins. Works on any phone. Pick it up between runs or at shift change — hours, not days, if leadership asks for it today.

Phone-friendly · SMS or email
iii.

Interview.

First we learn their shift. Then we dig into friction, systems, and the tasks they wish weren't theirs to re-do. Adapts as they answer.

10–15 min · voice or type
iv.

Report.

A prioritized shortlist of fixes — with direct quotes from the floor, hours-per-week cost, and effort-to-fix. You can act on it Monday.

Exports to PDF · CSV
§ 03 / The ascent

We start on the floor, not in the boardroom.

Most surveys ask the same question at every level. We don't. We start with the people closest to the work and carry their answers up the chain. By the time we talk to your COO, every question is already informed by what their team said.

i.

The floor.

Who we talk to · Operators, techs, maintenance, quality
Pass 01
What we ask

Walk me through a real Tuesday. Where does your shift go? What system fights you? What job do you run every single day that nobody upstairs seems to notice?

What we learn

Ground truth. Raw friction. The jobs, handoffs, and workarounds that make up actual work — regardless of how the SOP describes it.

Typical · 40 – 300 people
ii.

Shift supervisors & leads.

Who we talk to · First-line supervisors, schedulers
Pass 02
What we ask

Your line mentioned X fourteen times. Is that news? How much of your shift goes to unblocking it? What's your side of the handoff?

What we learn

Where the ground truth diverges from the reported picture. Which bottlenecks are known-and-accepted, and which are invisible from the floor below.

Typical · 8 – 30 people
iii.

Plant & functional leaders.

Who we talk to · Plant managers, ops & quality directors
Pass 03
What we ask

Three of your shifts re-key the same work order by hand. Your supervisors say it's “just how it is.” Who owns this process? What would it take to consolidate?

What we learn

Structural causes — incentives, ownership gaps, cross-department overhead — that no single line can see or solve on its own.

Typical · 3 – 8 people
iv.

The executive.

Who we talk to · CEO / COO / President
Pass 04
What we ask

Here is what the org actually does every shift — and here is what your ops plan assumed. These three gaps explain the margin you've been losing. Where do you want to invest?

What we learn

Alignment between intent and operation. The final map: strategy on top, ground truth underneath, every line of evidence traceable to a real voice.

Typical · 1 – 3 people
§ 04 / The interview

Real questions. In plain English. On their phone.

Every interview adjusts in real time. When someone mentions a recurring workaround, we follow up. When someone calls a handoff “fine,” we ask what it's for. Short by default. Deeper when it matters. No jargon the floor doesn't use.

9:42
Cirql · interview
6 / 12
Walk me through a typical Tuesday on Line 2. What takes up the biggest block of your shift?
Changeovers, mostly. And the morning huddle bleeds into an hour of chasing paperwork. I don't actually start running parts until about 9:30.
That “chasing paperwork” — is that you filling out forms, or waiting on the scheduler to release the work order?
Both. Mostly waiting on Quality to sign off on the last lot. I call, I wait, I walk back and forth.
Type your answer…
Line 2 operator · between runs

Your floor already knows where the drag is. Cirql gives them a space to say it — safely.

Anonymized by default. Summarized — never posted verbatim — unless the respondent opts in. Built so operators will actually finish it, not roll their eyes at it.

  • Works on any phone — no app, no login
  • Voice input or typing — whichever is easier on the floor
  • 15 minutes during a break, between runs, or at shift change
  • Adapts to their role, shift, and site
Median completion rate · 87%
§ 05 / The report

A prioritized list of things to fix. Not a dashboard.

A shortlist, not a wall of BI charts. Every finding has the evidence attached — quotes, frequency, hours cost, effort-to-fix — so you can make a call in the same meeting you open the report.

Field report · Ops org, Q2
18 pp · 62 interviews · 2 sites
i.
Every work order is re-keyed from the ERP into a spreadsheet

Schedulers export, edit, and re-import daily. Mentioned by 14 of 16 supervisors. Average time lost: 52 min per shift.

Quick win · ~3,200 hrs/yr
8.6Impact
ii.
Quality sign-off is a single-supervisor bottleneck

Every lot waits on one QA lead to release. Operators idle 20–45 min per changeover. Mentioned across all three shifts.

Staffing · cross-train
7.8Impact
iii.
Shift handoff happens eight different ways

Each supervisor logs it differently — clipboard, whiteboard, Teams DM, email to self. 6 of 8 said they'd welcome a single standard form.

Standardize
6.4Impact
iv.
Preventive-maintenance checklists are maintained by no one

New techs ask the same four questions their second week. Two maintenance leads update the book “when they get to it.” No owner.

Assign owner
5.1Impact
What's in the report

Findings, with the receipts attached.

Every claim links back to the raw interview evidence — quotes, frequency, which roles brought it up. You can forward the report to a skeptical exec and it'll hold up.

  • § iTime allocation — where hours actually go, by role, shift, and site
  • § iiSystem landscape — ERP, MES, spreadsheets, paper; overlaps and orphans
  • § iiiFriction log — ranked bottlenecks with quote-level evidence
  • § ivAutomation shortlist — ranked by hours saved vs. effort
  • § vAppendix — full transcripts, anonymized

You've already felt the drag.
Now see it.

Built for ops & plant leaders · $5M – $200M companies

Ten minutes to launch. Your people interview on their phones between runs. Same-day turnaround is on the table when you want it. You get a ranked list of things to fix — every shift, every role, every site.

$2,5004 runs over 12 months · unlimited respondents · one per quarter
Each run after the first is annotated against the last — what got fixed, what persists, what's new. Credited toward any Cirql build within 60 days of any run.