The Process

Five stages, same order, every engagement. Here's what happens before you commit to anything.

01 / BOTTLENECK AUDIT

First, we figure out what's actually happening.

Before recommending a tool or building anything, the work gets traced through the team as it actually happens: where information gets lost, where people repeat themselves, where the process quietly breaks down.

The problem usually isn't the tool. It's the workflow around it.

  • The same information gets typed into more than one system.
  • A spreadsheet is the real system of record.
  • Work requests arrive over WhatsApp, email, or a hallway conversation.
  • Nobody can say for certain who owns a task, or how far along it is.
FORM

↓

SPREADSHEET
← manual

↓

COPY / PASTE
← duplicate

↓

SLACK

↓

FOLLOW UP
← no owner

↓

SPREADSHEET

→ back to SPREADSHEET

3 MANUAL HANDOFFS

2 SOURCES OF TRUTH

4.2 HRS / WEEK

02 / DESIGN

Then we turn the mess into a plan.

What comes back is a clear picture of what's actually happening and what would change: a specific, written recommendation, before either of us commits to building anything.

The audit is useful even if you never hire me.

UNDERSTANDFINDINGSRECOMMENDATIONYOU DECIDE

WORKFLOW AUDIT

RECRUITING OPERATIONS

01
INTAKE / Manual, 12 min / application
02
SCREENING / Duplicate entry, 2 systems
03
COMMUNICATION / Manual follow-up, no ownership

KEY FINDINGS

03 bottlenecks / 02 duplicate processes

RECOMMENDATION

Automate intake / Centralize candidate state / Trigger communication

03 / PROTOTYPE

A working version, not a pitch.

A scoped, working proof on one part of the workflow, before the full rollout.

RECRUITING OPERATIONSApplication → screening → interview
CLIENT REPORTINGData sources → processing → report
INTERNAL REQUESTSEmail → structured request → ownership

TOKENFLOW / INTERNAL REQUESTS

View case study →

Here's the kind of thing we'd prototype: narrowed to one workflow slice, not the full system.

04 / IMPLEMENTATION

The system goes live, and the team owns it.

The workflow gets documented, training materials get created, and the people using the system every day understand what happens under the hood, not just how to click through it.

3 → 1 STAFF ON RECRUITMENT OPS

View case study →
✓ DOCUMENTED✓ TRAINED✓ HANDED OFF

We don't build mysterious machines that only we understand.

05 / OPTIMIZATION

And then we make it better.

30 days in, we review what's working and tune it, because the real ROI shows up after real usage.

MEASUREOBSERVEIMPROVEDEPLOY

SYSTEM / RECRUITING

V1
4 manual steps
V2
2 manual steps
V3
1 manual review
CURRENT
automated

LAST ITERATION / 12 SEP 2026

TIME SAVED / 4.2 HRS / WEEK

STATUS / ● ACTIVE

Start with where the time is going.

Chirag Kuinkel, founder of Levework
Chirag Kuinkel · Founder ↗

I'm Chirag. Building isn't the hard part anymore. Knowing what's worth building, and why, is. I find the process costing you the most, then build only the system that pays for itself. I don't sell software subscriptions.

15 minutes. Free. No obligation. If the right answer is “don't build anything,” I'll tell you that too.