asaday.
← All projects

Case study 04 / TMC Price Intelligence

From supplier inboxes to pricing intelligence.

An AI-assisted pricing workflow for Tomato Management Company that collects fragmented supplier information, makes it comparable, and puts it to work in quotes and invoices.

My role
AI Automation Engineer · Discovery to delivery
Status
Delivered engagement · 2023–2025
Built with
Email & attachment processing · AI extraction · Structured pricing data
TMC Price IntelligenceWorkflow / PRODUCT
FROM FRAGMENTED TO COMPARABLEThe price is in there.
Make it useful.
  1. CollectSupplier messages

    Emails, price lists, and attachments

  2. ExtractUseful fields

    Product, size, price, region, and supplier

  3. NormalizeComparable records

    A shared pricing repository with review

  4. UseOperational outputs

    Reports, quotes, and invoice workflows

80%

less pricing administration, reported engagement result

40%

faster processing, reported engagement result

35%

lower cloud spend, reported engagement result

01 / The problem

A pricing team should not have to rebuild the market by hand.

Produce prices arrive in the format a supplier happens to use: email text, a list, or an attachment. Product descriptions, sizes, and regional context vary. Before a team can compare offers or prepare a quote, someone has to find the information, interpret it, and put it in a consistent place.

At Tomato Management Company, I worked on the operational cost of that repetition. The goal was to make national pricing information accessible as usable records and reduce the administrative work between receiving an offer and acting on it.

02 / What I built

An extraction workflow with an operational destination.

The AI-assisted aggregator reads supplier communications and supporting files, extracts the useful pricing fields, and organizes the results for comparison. An early prototype used DeepSeek R1 in the interpretation step. Product type, size, price, region, and supplier become structured data rather than facts someone must rediscover in an inbox.

The work extended into a central pricing repository, reviewable reports, and quote and invoice workflows. That connection matters: a successful extraction is only valuable when the people making pricing decisions can use it without another round of copying and reformatting.

03 / The delivery work

Treat pricing as a workflow, not a single prompt.

I worked through stakeholder discovery, implementation, rollout, and production issues. The system had to account for inconsistent input, comparable product descriptions, and the review needed before an extracted value becomes a business decision. AI interpretation was one stage in that larger process.

Processing speed and infrastructure cost were also part of the engagement. A workflow that reduces manual effort but becomes expensive or difficult to operate simply moves the burden. The project therefore paired automation with changes to the way the processing and data were organized.

04 / Reported outcomes

Less administration. More usable information.

The recorded engagement outcomes report an 80% reduction in pricing administration, 40% faster processing, and 35% lower cloud spend. These are project-reported results from the 2023–2025 engagement, not a new independent benchmark or a guarantee for another business.

This is separate from my TMC website work. One project explains the company to buyers; this one improves the internal work behind sourcing, pricing, and commercial operations. Together they reflect the same approach: understand the business, then connect the software to what people actually need to do.

About this case study +

Recorded TMC engagement history, the supplier-email pricing prototype, and reported outcomes in my professional project record. This case study does not present a fresh production benchmark.

Researched and updated October 3, 2026.

Bring the problem

What are you
trying to make work?

Let’s talk about it ↗