Business process consulting

Fix the flow, one iteration at a time.

Shorter lead times and teams that can breathe, without a big overhaul or breaking what already works.

Three ways to start

Clear a specific bottleneck

Diagnostic

Deadlines slipping, teams stretched, work waiting in queues? We trace it back to the real cause and remove the block.

You leave with The root cause, explained plainly, and a first fix ready to try.

Ask for a diagnostic

Pinpoint your biggest gains

Assessment

What worked yesterday no longer keeps pace with your growth. We observe how work and data really move through your organization, and map where they pile up.

You leave with A map of your bottlenecks, ranked by impact, with metrics to track progress.

Ask for an assessment

Get answers from your data

Put your data to work

Your data sits in scattered files and tools, in different formats. We connect and clean it so it tells you what you need to know.

You leave with Reliable indicators, hidden delays made visible, and early warnings.

Talk about my data

Our approach, in practice

Four projects, one method

We work in short cycles: find the bottleneck, test a fix on a small scale, improve, then repeat.

Invoices out in 4 days instead of 12

A 60-person US services company was retyping billing data by hand, and invoices waited days for approval.

  • 12 → 4 daysfrom month-end to invoices sent
  • 1 in 5 → 1 in 50invoices rejected by clients
  • 8 dayscash collected sooner

Cycle 1

Clean data at the source

Find
Most rejections came from three errors: client codes, rates, missing PO numbers.
Test
One standard export with automatic checks, on the largest client account.
Improve
Extended to every account.

Cycle 2

Approvals that don’t wait

Find
Clean invoices still sat 5 to 6 days in managers’ inboxes.
Test
One shared approval queue with a 48-hour rule, with one team.
Improve
Became the standard for all teams.

No new software, no big-bang change.

Same fleet, 8 river trips every summer weekend

An Austin ground transport company had vehicles sitting idle on summer weekends, while groups heading to the river had no simple way to book a ride. We designed the booking process and pricing, built the site and tuned the operations.

  • 8river trips per summer weekend
  • 95%seats filled per trip
  • +20%revenue per trip

Cycle 1

The right vehicle for each group

Find
Groups had no simple way to book, and vehicle size was guessed case by case.
Test
A booking page where groups give their size and date, matched to a vehicle from the fleet, tried with a first set of groups.
Improve
Vehicle chosen from group size; the offer opened to all groups.

Cycle 2

Fill the empty seats

Find
Trips still left with empty seats, and some days had no group at all.
Test
Individual signup on a few set days, only to fill trips already scheduled.
Improve
The busiest days became fixed departures.

Cycle 3

Price by demand

Find
Busy days sold out early, while quiet days still had empty seats.
Test
Prices that adjust to the seats left in each vehicle size and to how far ahead people book, for groups and individuals.
Improve
Quiet days filled up, and busy days earned more.

No new vehicles: booking and pricing fill the ones already there.

1,000+ events per second behind a buyer-intent product

Before Iternov, our process consultant spent three years on the R&D team of a leading US B2B data company. There, he built a product that analyzes companies’ web activity to spot those preparing a purchase.

  • 1,000+events processed per second
  • 3 days soonerfor customers’ sales teams to reach companies ready to buy
  • 2 daysto put a new model version in production

Cycle 1

A pipeline that keeps up

Find
Engagement events arrived faster than the pipeline could process them, so weekly results ran late.
Test
An event pipeline built on queues and serverless functions, tried on one data stream.
Improve
Extended to every stream: 1,000+ events per second, weekly results ready the same day.

Cycle 2

Models into production, fast

Find
Models from university research partners took weeks to adapt to the production environment.
Test
Each model packaged in its own container and run beside the pipeline.
Improve
New model versions shipped without touching the pipeline.

The same method works inside an engineering team: one bottleneck at a time.

Tumor boards: from five scattered sources to one traceable decision

A private hospital group holds weekly tumor boards. Each patient file was rebuilt by hand from five systems, and decisions were made orally, with no record of who was present.

  • 5 → 1places to check per file
  • 0 → 100%decisions recorded in writing, with quorum
  • −50% (target)file preparation time, vs. today

Prototype

One page, one shared screen

Find
Five sources, each file organized differently, quorum lost when a specialist left.
Test
A prototype on fictional patients: documents classified, missing pieces flagged, a sheet drafted by a model hosted on site, every fact citing its source.
Improve
Quorum tracked case by case; a written, dated decision. Presented to the group’s leadership.

Pilot

Coming next: measure before scaling

Find
10 to 15 days observing two sessions to measure preparation time, incomplete files and deferrals.
Test
4 to 6 weeks running alongside today’s preparation, without changing it.
Improve
Compare, adjust, then decide on rollout.

The tool prepares, the doctor decides. Patient data never leaves the hospital.

About Iternov

Malek, founder of Iternov, smiling, in a blue blazer
Malek, founder · process consultant
  • 17years improving processes and systems
  • 1person, from the first call to the last cycle

Iternov brings your team the best practices and state-of-the-art tools acquired in US companies.

Let’s talk about your priorities

Tell us briefly about your situation. The button opens your email app with a message ready to send.

Or write to us directly:
contact@iternov.com

Nothing is sent from this site: your email app opens and you stay in control.