Talk about your next project
Nanonets case study

The lesson

Draw the customer's old manual process and the new pipeline as step diagrams, so a technical buyer can check the claim one step at a time.

The move

Two logos sit above a headline of two metrics, "100+ data rules applied per invoice. Real-time MSSQL export in 6 seconds.", followed by a one-paragraph summary, four stat chips and a Book a demo button. "About the customer" adds a firmographic strip. "The problem" sets a bulleted list beside a diagram of the manual steps from Gmail to an Excel spreadsheet, and an unnamed Director quote follows. "The solution" and "Pipeline overview" show the agent flow with a Replay control. A dark "Impact" block holds four stats, including 96% and 9/10, over a Metric, Before, After, Improvement table, and the page ends with "Agent anatomy" cards, an "Autonomous action-taking" diagram of exception paths, and "See it run on your process."

Why it works

  • Our readPutting the two metrics in the headline means a reader who reads one line gets the result before the story.
  • Our readThe before and after table turns each manual task from the problem list into a row, so the reader can match every pain to its fix.
  • Our readThe exception diagram shows what happens when a PO format is unrecognized or extraction confidence is low, which answers an operations buyer's first doubt about automation.

What not to copy

Don't copy the Gmail and MSSQL stack, the UK PO and charity code rules, or a quote credited only to a job title, since a named speaker carries more weight. Keep the metric headline with stat chips, the manual-process diagram beside the problem, the before and after table, and the closing diagram of exception handling.

More from Nanonets

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.