ProgrammableMarketing/lumari.ai (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

  • The brief
  • Start here
  • Idea portfolio
  • Effort vs impact
  • This week · 6
  • This quarter · 13
  • Big bets · 3
  • Wildcards · 3
Generated Nov 10, 2026
  1. Programmable
  2. Playbooks
  3. Lumari
Lumari logo

growth playbook · Nov 10, 2026

lumari.ai (opens in a new tab)

Lumari growth playbook

Diagnosis

Lumari is a five-person Y Combinator company with unusually strong proof for its stage: three published customers with hard numbers (10× faster RFQs at OFS, 20×+ faster RFQ-to-PO at Ultima Genomics, trusted dates on 100% of open POs at Carbon Robotics, all live in about two weeks).

The site is fast and well built, but its proof is in the wrong places: industry pages send life-sciences, electronics and aerospace buyers to a furniture story, quotes are credited by job title only, and the demo page has no proof at all. The blog published 44 posts in five months and then stopped in August, with no way to capture a reader.

This playbook first puts the right proof on every page, makes the integration and go-live claims consistent and opens a trust page. It then adds an hours calculator, an open-PO health check, a two-week pilot and head-to-head pages, and turns the data the agents already see into a supplier benchmark that rivals cannot copy.

Growth Score

7/10

Biggest Opportunity

Lumari already has the numbers buyers need (10×, 20×+, 100% trusted dates, live in two weeks). Matching them to each buyer's industry, ERP and pain, and offering a fixed two-week pilot, turns a founder-demo funnel into a repeatable one.

Biggest Risk

Better-funded rivals (Didero, SourceDay, Traza, plus suites such as JAGGAER and GEP) sell the same 'agents on top of your ERP' story, and with three published stories and a team of five, Lumari can lose deals on proof, not product.

01

Start here

The three moves to make first. Each one is written up in full below.

  1. 1

    Point each industry page to the customer story that matches it: life sciences to Ultima Genomics, not a furniture maker

    Change the life-sciences page's "Read more" link to the Ultima Genomics story and add its 20×+ result tile.

    High impact First result in 2 weeks
  2. 2

    Put the company name and a number next to every customer quote

    Tag each of the 12 quotes with its source customer in a sheet.

    High impact First result in 2 weeks
  3. 3

    Put proof and a clear agenda on the demo page, which today is only a calendar

    Write the three-line agenda and add it above the calendar.

    High impact First result in 2 weeks

02

Your idea portfolio

25 ideas, grouped by when to run them. Open any idea for how to run it: the steps, who to approach, copy you can use, and how to measure it.

  • 8 ideas are marked Unexpected: plays you are unlikely to have tried.

Every idea placed by the effort it takes against the impact it could have. Quick wins sit top left; select a number to open that idea. The filters below narrow the list by status, timing, category and what Programmable can build.

Effort vs impactEach number is an idea. Select one to open it.
Impact →
Quick wins · 5Big bets · 7Fill-ins · 6Reconsider · 7
Effort →

Showing 25 of 25 ideas

This week 6

Quick wins with a clear first action.

  • 01

    Lumari has eight industry pages, and each carries exactly one proof point: a quote credited only by job title and a "Read more" link. Five of the eight (aerospace & defense, semiconductors & electronics, life sciences & medical devices, automotive & mobility, chemicals & materials) send readers to the OFS story, a furniture manufacturer. The other three go to Carbon Robotics. No industry page links to Ultima Genomics, even though it is Lumari's life-sciences customer with the strongest numbers: 3,000+ part BOMs, 20×+ faster RFQ-to-PO and 99% fewer parts needing attention. A medical-device buyer who clicks "Read more" on the life-sciences page lands on office furniture, and none of the eight pages shows a single result number.

    High impactLow effort First result in 2 weeks Co founder

    First action

    Change the life-sciences page's "Read more" link to the Ultima Genomics story and add its 20×+ result tile.

    How to measure it

    Industry page to demo-calendar rate

    Now
    –
    Target
    +30%
    By
    60 days

    Steps

    1. 1

      Map pages to stories

      One table: each of the 8 industry pages, its closest customer, the result number and the quote to use.

      Co-founder (go-to-market) 2 hours

    2. 2

      Fix life sciences first

      Link to Ultima Genomics and add the 20×+ and 99% tile.

      Software Engineer 1 hour

    3. 3

      Build a result tile

      A reusable component: number, company, industry, systems (NetSuite, Arena, Slack).

      Software Engineer 1 day

    4. 4

      Swap quotes

      Use a quote from the matched story on each page.

      Co-founder (go-to-market) 2 hours

    5. 5

      Label near matches

      For chemicals and aerospace, say plainly that the story is from a manufacturer with a similar sourcing load.

      Co-founder (go-to-market) 1 hour

    6. 6

      Track clicks

      Analytics events for story clicks and demo-calendar views per industry page.

      Software Engineer 2 hours

    7. 7

      Review monthly

      Replace the near matches as new stories ship.

      Co-founder (go-to-market) monthly

    First result
    2 weeks
    Cost
    $0, about two days of work
    Owner
    Co founder (go to market)

    Smallest test

    Re-link the life-sciences page today and compare its story clicks and demo views over 30 days.

    Why it works

    Re-map the proof on all eight pages to the closest real customer and bring the number onto the page. Life sciences & medical devices → Ultima Genomics ("20×+ faster RFQ-to-PO", "99% fewer parts requiring team attention", NetSuite + Arena PLM). Semiconductors & electronics → Ultima Genomics for now (optics, electronics and fluidics in a 3,000-part BOM), until the electronics story marked "Coming soon" ships. Robotics & automation, advanced manufacturing, automotive & mobility and energy & infrastructure → Carbon Robotics (from 10–20% to 100% of open POs with trusted dates, live in under two weeks). Chemicals & materials and aerospace & defense → OFS for its RFQ numbers (10× faster, 2× faster landed cost), labelled honestly as "a manufacturer with a similar sourcing load". On every page, add a result tile above the quote (number, company, industry, systems used), use a quote from the matched story, and add a second link to the full Customers page. Then measure clicks from each industry page to its story and to the demo calendar.

    B2B buyers look for 'someone like me' before they book a call. The industry page is where search and outbound links land, so matching proof there costs nothing and removes the first doubt. The numbers already exist and are published; they are just on the wrong pages.

    Ready to use

    ChecklistIndustry page proof map

    Life sciences & medical devices -> Ultima Genomics: 20x+ faster RFQ-to-PO, 99% fewer parts needing attention
    Semiconductors & electronics -> Ultima Genomics (until the electronics story ships)
    Robotics & automation -> Carbon Robotics: 10-20% -> 100% open POs with trusted dates
    Advanced manufacturing -> Carbon Robotics
    Automotive & mobility -> Carbon Robotics
    Energy & infrastructure -> Carbon Robotics
    Chemicals & materials -> OFS: 10x faster RFQs, 2x faster landed cost (labelled near match)
    Aerospace & defense -> OFS (labelled near match)
    [ ] Result tile above each quote
    [ ] Quote taken from the matched story
    [ ] Click and demo-view tracking per page

    Risks and how to handle them

    • A customer did not approve its numbers for use beyond its own story

      Reuse only figures already published on the case-study pages, and tell each customer where they now appear.

    • Thin proof for aerospace and chemicals stays visible

      Label it honestly now and prioritise those industries for the next stories.

    Evidence

    • Your websiteIndustry pages (8, checked November 9, 2026): each shows one quote credited by job title only and one "Read more" link. Aerospace & defense, semiconductors & electronics, life sciences & medical devices, automotive & mobility and chemicals & materials all link to the OFS story (a furniture manufacturer); robotics & automation, energy & infrastructure and advanced manufacturing link to Carbon Robotics. No industry page links to the Ultima Genomics story, and none shows a result number.Source
    • Your websiteUltima Genomics case study (sequencing systems; product BOMs of 3,000+ parts; NetSuite, Arena PLM, Outlook and Teams): "20×+ faster RFQ-to-PO processing", "99% fewer parts requiring team attention", "100% supplier adoption"; "Instead of focusing on thousands of parts, we're focusing on the 20 that have issues" (Director of Global Supply Chain).Source
    • Your websiteCarbon Robotics case study (agricultural robots; Gmail, NetSuite, Slack): before Lumari only 10–20% of open POs had a delivery date the team trusted, and keeping orders current could take more than half of each buyer's week. Results: "100% of open POs have trusted delivery dates", implementation "under 2 weeks", 24/7 open-order monitoring, "100% supplier adoption"; "We didn't know something was going to be late until it was late."Source
    • Your websiteOFS case study (furniture maker since 1937): before Lumari one RFQ took 1–2 days to prepare, comparing 10–15 line items took over 2 hours, and manual sourcing took 20–25 hours a week. Results: "10× faster RFQ processing", "2× faster landed-cost comparison", "2 weeks implementation", "100% supplier adoption"; "Without Lumari, it would have taken three people to do what one person was able to do by himself" (Sourcing Manager).Source
    • Your websiteCustomers page: three stories (OFS, furniture; Carbon Robotics, robotics; Ultima Genomics, life sciences), two "Coming soon" tiles for Electronics Manufacturing and Industrial Manufacturing, and 12 quotes credited by role only (such as "Director of Global Supply Chain" and "Sourcing Coordinator") with no company named.Source
  • 02

    The Customers page carries 12 strong quotes ("What literally took us weeks happens instantly", "three people to do what one person was able to do"), but each is credited by role only, with no company. The same quotes reappear on the industry pages. Yet the case studies themselves name OFS, Carbon Robotics and Ultima Genomics. An anonymous "Director of Procurement" reads as weaker proof than the published story it comes from.

    High impactLow effort First result in 2 weeks Co founder

    First action

    Tag each of the 12 quotes with its source customer in a sheet.

    How to measure it

    Customers page demo rate

    Now
    –
    Target
    +20%
    By
    60 days

    Steps

    1. 1

      Trace each quote

      Match the 12 quotes to OFS, Carbon Robotics, Ultima Genomics or an unpublished customer.

      Co-founder (go-to-market) 2 hours

    2. 2

      Ask for approvals

      Confirm naming with any customer not yet published.

      Co-founder (go-to-market) 1 week

    3. 3

      Redesign the quote card

      Role, company, industry and one number.

      Software Engineer 1 day

    4. 4

      Add logos

      Three published customers on the homepage and Customers page.

      Software Engineer 2 hours

    5. 5

      Reuse on industry pages

      Same cards in the matched pages from idea 1.

      Software Engineer 2 hours

    6. 6

      Measure

      Demo-calendar views from the Customers page before and after.

      Co-founder (go-to-market) monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Co founder (go to market)

    Smallest test

    Credit the three Carbon Robotics and Ultima quotes by company today.

    Why it works

    For each of the 12 quotes, find its source story and show the company and industry next to the role ("Director of Procurement, Carbon Robotics"), plus the one number from that story. Where a quote comes from a customer that has not approved being named, ask for approval or keep it out of the strongest spots. Add logos for the three published customers to the Customers page and homepage.

    Named, specific proof is far more credible than anonymous praise. The approvals already exist for the three published stories, so most of this is formatting.

    Risks and how to handle them

    • Some customers will not be named

      Keep their quotes, but lead with the named ones.

    Builds on

    Evidence

    • Your websiteCustomers page: three stories (OFS, furniture; Carbon Robotics, robotics; Ultima Genomics, life sciences), two "Coming soon" tiles for Electronics Manufacturing and Industrial Manufacturing, and 12 quotes credited by role only (such as "Director of Global Supply Chain" and "Sourcing Coordinator") with no company named.Source
    • Your websiteIndustry pages (8, checked November 9, 2026): each shows one quote credited by job title only and one "Read more" link. Aerospace & defense, semiconductors & electronics, life sciences & medical devices, automotive & mobility and chemicals & materials all link to the OFS story (a furniture manufacturer); robotics & automation, energy & infrastructure and advanced manufacturing link to Carbon Robotics. No industry page links to the Ultima Genomics story, and none shows a result number.Source
    • Your websiteOFS case study (furniture maker since 1937): before Lumari one RFQ took 1–2 days to prepare, comparing 10–15 line items took over 2 hours, and manual sourcing took 20–25 hours a week. Results: "10× faster RFQ processing", "2× faster landed-cost comparison", "2 weeks implementation", "100% supplier adoption"; "Without Lumari, it would have taken three people to do what one person was able to do by himself" (Sourcing Manager).Source
  • 03

    Every page ends in "Book a Demo", and the destination is a calendar for "an intro call" with the founders, with no customer quote, no number and no word on what the call covers or what happens next. The site's real visitors get fast pages (they pass Core Web Vitals), so the drop-off risk here is doubt, not speed.

    High impactLow effort First result in 2 weeks Co founder

    First action

    Write the three-line agenda and add it above the calendar.

    How to measure it

    Contact page booking rate

    Now
    –
    Target
    +25%
    By
    45 days

    Steps

    1. 1

      Write the agenda

      Three lines on what the call covers.

      Co-founder (go-to-market) 1 hour

    2. 2

      Add result tiles

      10×, 20×+ and 100% trusted dates with company names.

      Software Engineer 2 hours

    3. 3

      Add three answers

      ERP fit, nothing new for suppliers, security.

      Co-founder (go-to-market) 2 hours

    4. 4

      Add prep questions

      Optional ERP and main pain fields in the booking flow.

      Software Engineer 2 hours

    5. 5

      Send a pre-call note

      Confirmation email with the matching case study.

      Co-founder (go-to-market) 1 day

    6. 6

      Track show rate

      Bookings, no-shows and pilots started.

      Co-founder (go-to-market) weekly

    First result
    2 weeks
    Cost
    $0
    Owner
    Co founder (go to market)

    Smallest test

    Add the agenda and one result tile, and compare bookings for two weeks.

    Why it works

    Above the calendar, add a three-line agenda (your current RFQ and PO flow, a live run on one of your own quotes or open POs, a pilot plan), three result tiles (10×, 20×+, 100% trusted dates) and "live in under two weeks". Below it, add short answers on ERP fit, suppliers needing nothing new, and security. Offer a short optional question (ERP and main pain) so the founders can prepare.

    A buyer who knows what they will get from the call, and sees peers' results at the moment of booking, is more likely to book and to show up.

    Risks and how to handle them

    • Extra questions lower bookings

      Keep them optional.

    Evidence

    • Your websiteContact page: "Book an intro call" with the founders through an embedded Cal.com calendar; no form, no customer quotes, no case-study numbers and nothing on pilots or pricing.Source
    • Google PageSpeedHomepage scores 99 on mobile and desktop, accessibility 97 (one colour-contrast issue), SEO 100; real visitors pass Core Web Vitals (LCP 881 ms, INP 62 ms, CLS 0), and LCP is 31% faster than in the previous period.Source
    • Your websiteCarbon Robotics case study (agricultural robots; Gmail, NetSuite, Slack): before Lumari only 10–20% of open POs had a delivery date the team trusted, and keeping orders current could take more than half of each buyer's week. Results: "100% of open POs have trusted delivery dates", implementation "under 2 weeks", 24/7 open-order monitoring, "100% supplier adoption"; "We didn't know something was going to be late until it was late."Source
  • 04

    The homepage lists Gmail, SAP, NetSuite, Oracle, JDE, Vista and Procore. The Lumari vs SourceDay post adds Epicor. The blog has a full Dynamics 365 guide, but Dynamics is not in the homepage list. The case studies show Outlook, Microsoft Teams and Arena PLM, none of which is named as an integration. Buyers screen vendors on 'does it work with our ERP' and get three different answers.

    Medium impactLow effort First result in 1 month Co founder

    First action

    List every system named anywhere on the site and mark which ones are live with customers.

    How to measure it

    ERP-fit objections on calls

    Now
    –
    Target
    -50%
    By
    90 days

    Steps

    1. 1

      Inventory claims

      Homepage, blog guides, comparison posts and case studies.

      Co-founder (product and engineering) 2 hours

    2. 2

      Group them

      Live, supported, on request.

      Co-founder (product and engineering) 1 hour

    3. 3

      Build one component

      A single source rendered everywhere.

      Software Engineer 1 day

    4. 4

      Replace old lists

      Homepage, SourceDay post, ERP guides.

      Software Engineer 2 hours

    5. 5

      Link proof

      NetSuite to Carbon Robotics and Ultima; Arena to Ultima.

      Software Engineer 1 hour

    6. 6

      Log objections

      Note ERP questions on each demo.

      Co-founder (go-to-market) ongoing

    First result
    1 month
    Cost
    $0
    Owner
    Co founder (product and engineering)

    Smallest test

    Add Dynamics 365, Epicor, Outlook and Arena to the homepage list with their real status.

    Why it works

    Agree one canonical list in three groups: live with customers (NetSuite, Gmail, Outlook, Slack, Teams, Arena), supported, and built on request. Show it on the homepage, in each ERP guide and in comparison posts. Add 'proven at' links to the case studies next to NetSuite and Arena.

    Consistent, specific integration claims build trust and stop deals being lost at the first screen.

    Risks and how to handle them

    • A shorter 'live' list looks smaller

      Show the on-request tier and say how long a new connector takes.

    Evidence

    • Your websiteHomepage: an "AI supply chain platform" for direct procurement (YC X25) with agents for RFQs, quote extraction, BOM processing, PO tracking, compliance data (country of origin, HS codes, RoHS, conflict minerals) and landed cost; suppliers keep replying by email with no portal; integrations listed as Gmail, SAP, NetSuite, Oracle, JDE, Vista and Procore, plus Slack and Microsoft Teams; the only call to action is "Book a Demo" and there is no pricing page.Source
    • Your website"Lumari vs SourceDay" (updated April 22, 2026), the only head-to-head page: the text says teams "go live in days" while its own table lists Lumari's "Time to go live" as "Weeks"; it says Lumari "connects to SAP, Oracle, NetSuite, Epicor, and others" (Epicor is not in the homepage list).Source
    • Your websiteBlog: 44 posts from March 13 to August 17, 2026 (about two a week), none since August 17; categories Comparison, Guide, Insight, Operations and Automation; ERP guides for SAP, NetSuite and Dynamics 365; no newsletter signup, template download or calculator, only "Book a Demo".Source
    • Your websiteUltima Genomics case study (sequencing systems; product BOMs of 3,000+ parts; NetSuite, Arena PLM, Outlook and Teams): "20×+ faster RFQ-to-PO processing", "99% fewer parts requiring team attention", "100% supplier adoption"; "Instead of focusing on thousands of parts, we're focusing on the 20 that have issues" (Director of Global Supply Chain).Source
  • 05

    The SourceDay comparison says teams "go live in days", while the table on the same page says "Weeks". Meanwhile OFS went live in "2 weeks" and Carbon Robotics in "under 2 weeks". Didero leads with "18 days from ERP connect to first end-to-end automation". Lumari has a better, proven number and is blurring it.

    Medium impactLow effort First result in 1 week Co founder

    First action

    Correct the SourceDay comparison so the text and table both say "under two weeks".

    How to measure it

    Go-live claim consistency across pages

    Now
    –
    Target
    100% of pages
    By
    2 weeks

    Steps

    1. 1

      Agree the wording

      One sentence and its conditions.

      Co-founder (go-to-market) 1 hour

    2. 2

      Fix the comparison

      Text and table on the SourceDay post.

      Software Engineer 1 hour

    3. 3

      Add it site-wide

      Homepage, industry pages, demo page.

      Software Engineer 2 hours

    4. 4

      Link the proof

      OFS and Carbon Robotics stories.

      Software Engineer 1 hour

    5. 5

      Track go-live

      Days from kickoff to first live agent for each new customer.

      Founding Forward Deployed Engineer ongoing

    6. 6

      Review quarterly

      Tighten the claim if the median falls.

      Co-founder (go-to-market) quarterly

    First result
    1 week
    Cost
    $0
    Owner
    Co founder (go to market)

    Smallest test

    Fix the comparison post today.

    Why it works

    Adopt one claim, "live in under two weeks, with every supplier included from day one", linked to the two case studies. Fix the comparison table and text, add the claim to the homepage, industry pages and demo page, and track actual go-live time for every new customer so the number stays true.

    A specific, provable time-to-value claim beats vague speed, and it is directly comparable with a rival's 18 days.

    Risks and how to handle them

    • A complex ERP takes longer

      State the claim for supported systems and give a range for the rest.

    Evidence

    • Your website"Lumari vs SourceDay" (updated April 22, 2026), the only head-to-head page: the text says teams "go live in days" while its own table lists Lumari's "Time to go live" as "Weeks"; it says Lumari "connects to SAP, Oracle, NetSuite, Epicor, and others" (Epicor is not in the homepage list).Source
    • Your websiteOFS case study (furniture maker since 1937): before Lumari one RFQ took 1–2 days to prepare, comparing 10–15 line items took over 2 hours, and manual sourcing took 20–25 hours a week. Results: "10× faster RFQ processing", "2× faster landed-cost comparison", "2 weeks implementation", "100% supplier adoption"; "Without Lumari, it would have taken three people to do what one person was able to do by himself" (Sourcing Manager).Source
    • Your websiteCarbon Robotics case study (agricultural robots; Gmail, NetSuite, Slack): before Lumari only 10–20% of open POs had a delivery date the team trusted, and keeping orders current could take more than half of each buyer's week. Results: "100% of open POs have trusted delivery dates", implementation "under 2 weeks", 24/7 open-order monitoring, "100% supplier adoption"; "We didn't know something was going to be late until it was late."Source
    • Competitor researchRivals' own homepages: Didero, "Supply chains on autopilot" for manufacturers and distributors, with a "Run Your Numbers" ROI calculator and "18 days from ERP connect to first end-to-end automation"; SourceDay, "The #1 PO Management Solution for Manufacturers & Distributors", "123K suppliers activated", named customer results and a Supplier Reliability Index (Fall 2026) report; Traza, role-specific procurement agents with a long integrations list including Microsoft Dynamics, Coupa and Procore.Source
  • 06

    Lumari gives agents access to buyers' inboxes, ERPs and supplier pricing. Its security page lists SOC 2 Type I and II and CASA Tier II, but the SOC 2 report and the subprocessor list are only available by email, there is no trust center, and the page says nothing on data residency or whether customer data is used to train models. Those are the first questions an IT or security reviewer asks.

    Medium impactLow effort First result in 1 quarter Co founder

    First action

    Write the one-paragraph answer on model training and data use.

    How to measure it

    Median days from security questionnaire to approval

    Now
    –
    Target
    -30%
    By
    1 quarter

    Steps

    1. 1

      List top questions

      From the last ten security reviews.

      Co-founder (product and engineering) 1 day

    2. 2

      Write answers

      Data access, residency, retention, training, subprocessors.

      Co-founder (product and engineering) 2 days

    3. 3

      Legal check

      Make sure answers match the contract.

      Outside counsel 1 week

    4. 4

      Publish the page

      With a report request button.

      Software Engineer 1 day

    5. 5

      Link it

      Demo page, industry pages, footer.

      Software Engineer 1 hour

    6. 6

      Measure

      Review length on new deals.

      Co-founder (go-to-market) quarterly

    First result
    1 quarter
    Cost
    Staff time and a short legal review
    Owner
    Co founder (product and engineering)

    Smallest test

    Add the data-use and subprocessor answers to the existing security page.

    Why it works

    Add a short trust page: what data the agents can read and write, where it is stored, retention, whether customer data trains models (and the contractual promise), the subprocessor list, and a request button for the SOC 2 report under NDA. Link it from the demo page and the industry pages.

    Security review is often the slowest step in mid-market deals. Answering in public shortens it and signals maturity beyond a five-person team.

    Risks and how to handle them

    • Public answers become commitments

      Have counsel check them against the contract first.

    Evidence

    • Your websiteSecurity page: SOC 2 Type I and Type II and CASA Tier II; the SOC 2 report and subprocessor list are available on email request; no trust center; nothing on data residency or on whether customer data is used to train models.Source
    • HiringThree open roles on Y Combinator's job board, all in San Francisco, at a team of 5 founded in 2025: a Founding Forward Deployed Engineer ($110K–$170K, 0.25%–3.00% equity) who works with the founders on the largest customer engagements, turns customer workflows into implementations and builds production agents; a Software Engineer; and a "Former Founders" role spanning product, engineering, operations and go-to-market.Source

This quarter 13

The core plays for the next three months.

  • 07

    Lumari's most useful blog post already does the math (medium RFQs take "16 to 54 days", buyers spend about 20 hours a week on follow-ups, admin time costs "roughly $48,000 per person per year"), but readers can't put in their own numbers. OFS's baseline (1–2 days per RFQ, 2+ hours to compare 10–15 lines) and its 10× result are the perfect inputs. Didero already offers a "Run Your Numbers" calculator.

    High impactMedium effort First result in 1 month Software Engineer

    First action

    Write the formula from the manual-RFQ post and OFS's baseline.

    How to measure it

    Calculator-to-demo rate

    Now
    –
    Target
    15%
    By
    90 days

    Steps

    1. 1

      Write the model

      Inputs, formulas and ranges from the post and case studies.

      Co-founder (go-to-market) 2 days

    2. 2

      Design

      Five inputs, one result screen.

      Software Engineer 2 days

    3. 3

      Build

      On the site, with no login.

      Software Engineer 1 week

    4. 4

      Add the PDF

      Emailed summary for finance.

      Software Engineer 2 days

    5. 5

      Place it

      Manual-RFQ post, business-case post, demo page.

      Software Engineer 1 day

    6. 6

      Follow up

      Founder email referencing the buyer's own numbers.

      Co-founder (go-to-market) ongoing

    First result
    1 month
    Cost
    About two weeks of engineering
    Owner
    Software Engineer

    Smallest test

    Embed a static worked example table in the manual-RFQ post first.

    Why it works

    Build a simple calculator: buyers on the team, RFQs a month, average lines per RFQ, open POs, share of POs with a trusted date. Output hours and dollars spent today, and the range Lumari customers achieved (10× RFQ, 2× landed cost, 100% trusted dates). Show the result at once and offer a PDF copy for an email, to share with a CFO.

    Procurement leaders need a number to take to finance. Using real customer results makes the output credible and gives the founders a warm, quantified lead.

    Risks and how to handle them

    • Overstated savings

      Show ranges and link each one to the customer it comes from.

    Evidence

    • Your website"How Much Time Does Manual RFQ Management Actually Cost?": a medium-complexity RFQ takes "16 to 54 days"; buyers report "roughly 20 hours per week on follow-up communications"; admin time costs "roughly $48,000 per person per year", "close to half a million dollars per year" for a 10-person team; the post has no calculator or download.Source
    • Your websiteOFS case study (furniture maker since 1937): before Lumari one RFQ took 1–2 days to prepare, comparing 10–15 line items took over 2 hours, and manual sourcing took 20–25 hours a week. Results: "10× faster RFQ processing", "2× faster landed-cost comparison", "2 weeks implementation", "100% supplier adoption"; "Without Lumari, it would have taken three people to do what one person was able to do by himself" (Sourcing Manager).Source
    • Competitor researchRivals' own homepages: Didero, "Supply chains on autopilot" for manufacturers and distributors, with a "Run Your Numbers" ROI calculator and "18 days from ERP connect to first end-to-end automation"; SourceDay, "The #1 PO Management Solution for Manufacturers & Distributors", "123K suppliers activated", named customer results and a Supplier Reliability Index (Fall 2026) report; Traza, role-specific procurement agents with a long integrations list including Microsoft Dynamics, Coupa and Procore.Source
  • 08

    Carbon Robotics' starting point was striking: only 10–20% of open POs had a delivery date the team trusted. Most buyers have never measured this. Lumari's agents already read supplier replies and compare them with ERP dates, so a one-off check of an open-PO export is a small version of the product itself.

    High impactMedium effort First result in 1 month Founding Forward Deployed Eng…

    First action

    Write the one-page result template using Carbon Robotics' before and after as the example.

    How to measure it

    Health-check to pilot rate

    Now
    –
    Target
    30%
    By
    1 quarter

    Steps

    1. 1

      Define the check

      Four measures and the input format.

      Founding Forward Deployed Engineer 2 days

    2. 2

      Build the report

      One page, generated from the export.

      Founding Forward Deployed Engineer 1 week

    3. 3

      Set data rules

      NDA, deletion after 30 days, read-only.

      Co-founder (product and engineering) 2 days

    4. 4

      Landing page

      What you send, what you get, in how long.

      Software Engineer 2 days

    5. 5

      Promote

      Founder LinkedIn posts and outbound to NetSuite manufacturers.

      Co-founder (go-to-market) ongoing

    6. 6

      Review on a call

      Walk through results and propose a pilot.

      Co-founder (go-to-market) per lead

    First result
    1 month
    Cost
    Engineering time; a few hours per check
    Owner
    Founding Forward Deployed Engineer

    Smallest test

    Run the check by hand for three prospects this month.

    Why it works

    Invite buyers to send an open-PO report (or connect read-only for one week). Return a one-page result: POs with no acknowledgement, ERP dates that don't match the supplier's latest reply, past-due lines, and the top suppliers causing risk. Present it on a call with a pilot plan.

    It turns an abstract pitch into the buyer's own number, and it qualifies the lead: a team at 20% trusted dates has a budgetable problem.

    Risks and how to handle them

    • Too much manual work per check

      Accept only standard ERP exports at first and cap the number each week.

    Evidence

    • Your websiteCarbon Robotics case study (agricultural robots; Gmail, NetSuite, Slack): before Lumari only 10–20% of open POs had a delivery date the team trusted, and keeping orders current could take more than half of each buyer's week. Results: "100% of open POs have trusted delivery dates", implementation "under 2 weeks", 24/7 open-order monitoring, "100% supplier adoption"; "We didn't know something was going to be late until it was late."Source
    • HiringThree open roles on Y Combinator's job board, all in San Francisco, at a team of 5 founded in 2025: a Founding Forward Deployed Engineer ($110K–$170K, 0.25%–3.00% equity) who works with the founders on the largest customer engagements, turns customer workflows into implementations and builds production agents; a Software Engineer; and a "Former Founders" role spanning product, engineering, operations and go-to-market.Source
  • 09

    Lumari's own business-case guide tells buyers to run a pilot, and both OFS and Carbon Robotics went live in about two weeks. But the site offers only a founder intro call: no pilot, no scope, no price signal. Buyers must invent the next step themselves.

    High impactLow effort First result in 1 month Co founder

    First action

    Write the scope and success measure for the open-PO pilot.

    How to measure it

    Demo-to-pilot rate

    Now
    –
    Target
    35%
    By
    1 quarter

    Steps

    1. 1

      Define two pilots

      Open-PO follow-up and RFQ sprint.

      Co-founder (go-to-market) 2 days

    2. 2

      Set the fee

      Fixed, credited to year one.

      Co-founder (go-to-market) 1 day

    3. 3

      Write the playbook

      Day-by-day plan to go live in two weeks.

      Founding Forward Deployed Engineer 1 week

    4. 4

      Publish the page

      Scope, timing, success measure, proof.

      Software Engineer 2 days

    5. 5

      Offer on every demo

      Close each call with the pilot proposal.

      Co-founder (go-to-market) ongoing

    6. 6

      Report results

      Pilot results become the next case studies.

      Co-founder (go-to-market) per pilot

    First result
    1 month
    Cost
    Staff time
    Owner
    Co founder (go to market)

    Smallest test

    Offer the open-PO pilot on the next five demos.

    Why it works

    Define one pilot per entry point: 'Open-PO follow-up' (one ERP, one buyer's suppliers, target trusted dates on 90%+ of open POs) and 'RFQ sprint' (ten live RFQs, target time to comparison). Fixed scope, two weeks to live, a 30-day run, a known fee credited to the first year. Publish a short pilot page and link it from the demo page.

    A named, low-risk next step shortens sales cycles and lets a champion get budget without a full purchase decision.

    Risks and how to handle them

    • Pilots that never convert

      Agree the conversion terms and success measure in writing before the start.

    Builds on

    Evidence

    • Your websiteContact page: "Book an intro call" with the founders through an embedded Cal.com calendar; no form, no customer quotes, no case-study numbers and nothing on pilots or pricing.Source
    • Your websiteOFS case study (furniture maker since 1937): before Lumari one RFQ took 1–2 days to prepare, comparing 10–15 line items took over 2 hours, and manual sourcing took 20–25 hours a week. Results: "10× faster RFQ processing", "2× faster landed-cost comparison", "2 weeks implementation", "100% supplier adoption"; "Without Lumari, it would have taken three people to do what one person was able to do by himself" (Sourcing Manager).Source
    • Your websiteCarbon Robotics case study (agricultural robots; Gmail, NetSuite, Slack): before Lumari only 10–20% of open POs had a delivery date the team trusted, and keeping orders current could take more than half of each buyer's week. Results: "100% of open POs have trusted delivery dates", implementation "under 2 weeks", 24/7 open-order monitoring, "100% supplier adoption"; "We didn't know something was going to be late until it was late."Source
    • Your websiteHomepage: an "AI supply chain platform" for direct procurement (YC X25) with agents for RFQs, quote extraction, BOM processing, PO tracking, compliance data (country of origin, HS codes, RoHS, conflict minerals) and landed cost; suppliers keep replying by email with no portal; integrations listed as Gmail, SAP, NetSuite, Oracle, JDE, Vista and Procore, plus Slack and Microsoft Teams; the only call to action is "Book a Demo" and there is no pricing page.Source
  • 10

    "Best AI for Direct Procurement (2026)" names twelve vendors, from LightSource and Keelvar to JAGGAER and Coupa, but SourceDay is the only one with its own "Lumari vs" page. Newer agent rivals such as Didero and Traza have none, and the roundup links no case study.

    High impactMedium effort First result in 2 months Co founder

    First action

    Ask the last ten prospects which other vendors they looked at.

    How to measure it

    Comparison-page demo bookings

    Now
    –
    Target
    10 a month
    By
    2 quarters

    Steps

    1. 1

      Pick rivals

      From deal notes and the roundup.

      Co-founder (go-to-market) 1 day

    2. 2

      Check facts

      Each rival's own site, dated.

      Co-founder (go-to-market) 1 week

    3. 3

      Write pages

      Same structure as the SourceDay page, with a proof link.

      Co-founder (go-to-market) 2 weeks

    4. 4

      Review claims

      Trademarks and accuracy.

      Outside counsel 1 week

    5. 5

      Link them

      From the roundup and industry pages.

      Software Engineer 1 day

    6. 6

      Refresh

      Every quarter.

      Co-founder (go-to-market) quarterly

    First result
    2 months
    Cost
    Writing time and a short legal review
    Owner
    Co founder (go to market)

    Smallest test

    Publish one page versus Didero and track its demos.

    Why it works

    Publish fair comparisons for the rivals buyers raise most: Didero, LightSource, Keelvar, JAGGAER and Coupa. Each covers scope (RFQ to delivery), supplier adoption (portal or email), time to live, ERP fit, and when the rival is the better choice, with a matching case study. Link them from the roundup and add case-study links inside it.

    Comparison searches come from buyers who are already shortlisting, and fair pages win trust and AI-assistant answers.

    Risks and how to handle them

    • Claims go out of date

      Date each page and cite the rival's own pages.

    Builds on

    Evidence

    • Your website"Best AI for Direct Procurement (2026)" (updated July 7, 2026) names LightSource, Keelvar, SourceDay, JAGGAER, Ivalua, GEP SMART, SAP Ariba, Coupa, Oracle Procurement Cloud, Suplari, Levelpath and Zip; the article body links no case study.Source
    • Your website"Lumari vs SourceDay" (updated April 22, 2026), the only head-to-head page: the text says teams "go live in days" while its own table lists Lumari's "Time to go live" as "Weeks"; it says Lumari "connects to SAP, Oracle, NetSuite, Epicor, and others" (Epicor is not in the homepage list).Source
    • Competitor researchRivals' own homepages: Didero, "Supply chains on autopilot" for manufacturers and distributors, with a "Run Your Numbers" ROI calculator and "18 days from ERP connect to first end-to-end automation"; SourceDay, "The #1 PO Management Solution for Manufacturers & Distributors", "123K suppliers activated", named customer results and a Supplier Reliability Index (Fall 2026) report; Traza, role-specific procurement agents with a long integrations list including Microsoft Dynamics, Coupa and Procore.Source
  • 11

    Lumari published 44 posts between March 13 and August 17, 2026 (about two a week), then nothing for nearly three months. The posts are mostly definitions and guides (RFQ, Incoterms, 3-way match). The customer data that makes Lumari different (3,000-part BOMs, trusted dates going from 10–20% to 100%) rarely appears in them.

    Medium impactMedium effort First result in 2 months Founding GTM hire

    First action

    Draft the Ultima Genomics 'thousands of parts to 20' post.

    How to measure it

    Blog-sourced demos

    Now
    –
    Target
    +50%
    By
    2 quarters

    Steps

    1. 1

      Set the calendar

      Twelve weeks, four post types.

      Founding GTM hire (Former Founders role) 2 days

    2. 2

      Interview customers

      One 30-minute call per story.

      Co-founder (go-to-market) 2 weeks

    3. 3

      Write weekly

      One post each week.

      Founding GTM hire (Former Founders role) weekly

    4. 4

      Refresh top guides

      Add proof and links to case studies.

      Founding GTM hire (Former Founders role) monthly

    5. 5

      Distribute

      Founder LinkedIn posts for each one.

      Co-founder (go-to-market) weekly

    6. 6

      Measure

      Demos and assisted demos by post.

      Founding GTM hire (Former Founders role) monthly

    First result
    2 months
    Cost
    Writer time or a freelance budget
    Owner
    Founding GTM hire (Former Founders role)

    Smallest test

    Publish one customer-number post and compare it with the average guide.

    Why it works

    Restart at one post a week, with a different mix: one 'how a customer did it' post a month from each story (for example how Ultima's buyers moved from thousands of parts to the 20 with issues), one ERP-specific playbook, one comparison, and one refresh of a top older guide with a case-study link. Add a 'last updated' date and an author to each.

    Steady publishing keeps search and AI answers fresh, and proof-led posts convert better than definitions.

    Risks and how to handle them

    • Cadence slips again

      Batch-write four posts ahead.

    Evidence

    • Your websiteBlog: 44 posts from March 13 to August 17, 2026 (about two a week), none since August 17; categories Comparison, Guide, Insight, Operations and Automation; ERP guides for SAP, NetSuite and Dynamics 365; no newsletter signup, template download or calculator, only "Book a Demo".Source
    • Your websiteUltima Genomics case study (sequencing systems; product BOMs of 3,000+ parts; NetSuite, Arena PLM, Outlook and Teams): "20×+ faster RFQ-to-PO processing", "99% fewer parts requiring team attention", "100% supplier adoption"; "Instead of focusing on thousands of parts, we're focusing on the 20 that have issues" (Director of Global Supply Chain).Source
    • HiringThree open roles on Y Combinator's job board, all in San Francisco, at a team of 5 founded in 2025: a Founding Forward Deployed Engineer ($110K–$170K, 0.25%–3.00% equity) who works with the founders on the largest customer engagements, turns customer workflows into implementations and builds production agents; a Software Engineer; and a "Former Founders" role spanning product, engineering, operations and go-to-market.Source
  • 12

    Forty-four posts and a 61-term glossary bring procurement readers in, but there is no newsletter, template or download anywhere. The only option is "Book a Demo", which most early-stage readers are not ready for. Every reader who leaves without booking is lost.

    Medium impactLow effort First result in 1 month Founding GTM hire

    First action

    Turn the PO follow-up post into a downloadable chase-sequence template.

    How to measure it

    New subscribers per month

    Now
    –
    Target
    150
    By
    1 quarter

    Steps

    1. 1

      Build the pack

      Three templates from existing posts.

      Founding GTM hire (Former Founders role) 1 week

    2. 2

      Add capture

      Inline and end-of-post signup.

      Software Engineer 2 days

    3. 3

      Write the nurture

      Five emails: template, story, calculator, pilot.

      Founding GTM hire (Former Founders role) 1 week

    4. 4

      Start the monthly note

      One supplier insight, one story, one guide.

      Founding GTM hire (Former Founders role) monthly

    5. 5

      Alert sales

      Flag engaged readers from target-size companies.

      Co-founder (go-to-market) ongoing

    6. 6

      Measure

      Subscribers to demos.

      Founding GTM hire (Former Founders role) monthly

    First result
    1 month
    Cost
    Email tool subscription
    Owner
    Founding GTM hire (Former Founders role)

    Smallest test

    Add one template download to the three most-read posts.

    Why it works

    Offer two things on every post: a practical template pack (RFQ email set, PO acknowledgement chase sequence, quote-comparison sheet with landed-cost columns, the same work Lumari automates), and a monthly note for direct-procurement leaders. Nurture with case studies and the calculator, and alert the founders when a reader from a target-size manufacturer engages.

    Procurement buying cycles are long. Capturing readers early builds a pipeline the founders can work when the need appears.

    Risks and how to handle them

    • Low-quality signups

      Ask for company and role, and score by company size.

    Evidence

    • Your websiteBlog: 44 posts from March 13 to August 17, 2026 (about two a week), none since August 17; categories Comparison, Guide, Insight, Operations and Automation; ERP guides for SAP, NetSuite and Dynamics 365; no newsletter signup, template download or calculator, only "Book a Demo".Source
    • Your websiteGlossary: "61 terms across 6 topics" (such as OTIF, EDI 855, promise date, landed cost and approved manufacturer list) on one page, each with a "Related guide" link to the blog; no page per term.Source
    • Your websiteChannels: LinkedIn is the only social profile linked from the site; no YouTube, X or newsletter; lumari.io redirects permanently to lumari.ai.Source
  • 13

    The Customers page shows two "Coming soon" tiles, Electronics Manufacturing and Industrial Manufacturing. The semiconductors & electronics page currently sends readers to a furniture story. Placeholders tell a buyer the proof is not there yet.

    Medium impactMedium effort First result in 6 weeks Co founder

    First action

    Agree the headline number and approval with the electronics customer.

    How to measure it

    Live customer stories

    Now
    –
    Target
    5
    By
    1 quarter

    Steps

    1. 1

      Confirm customers

      Approval and an interview slot.

      Co-founder (go-to-market) 1 week

    2. 2

      Pull data

      Before and after from the platform.

      Founding Forward Deployed Engineer 1 week

    3. 3

      Interview

      Procurement lead and one buyer.

      Co-founder (go-to-market) 1 week

    4. 4

      Write and approve

      Same format as Carbon Robotics.

      Founding GTM hire (Former Founders role) 2 weeks

    5. 5

      Publish and re-link

      Replace the tile; update industry pages.

      Software Engineer 1 day

    6. 6

      Hide if late

      Remove tiles not ready in six weeks.

      Software Engineer 1 hour

    First result
    6 weeks
    Cost
    Staff time
    Owner
    Co founder (go to market)

    Smallest test

    Publish a short results card for electronics before the full story.

    Why it works

    Finish the electronics story first, with a number on alternates or allocation (the electronics page's own promise), then the industrial one. If either needs more than six weeks, remove the tile until it is ready. Update the matching industry pages from idea 1.

    Each new story opens a vertical's search, outbound and industry-page proof at once.

    Risks and how to handle them

    • Customer approval stalls

      Offer an anonymised version with the industry and numbers.

    Builds on

    Evidence

    • Your websiteCustomers page: three stories (OFS, furniture; Carbon Robotics, robotics; Ultima Genomics, life sciences), two "Coming soon" tiles for Electronics Manufacturing and Industrial Manufacturing, and 12 quotes credited by role only (such as "Director of Global Supply Chain" and "Sourcing Coordinator") with no company named.Source
    • Your websiteIndustry pages (8, checked November 9, 2026): each shows one quote credited by job title only and one "Read more" link. Aerospace & defense, semiconductors & electronics, life sciences & medical devices, automotive & mobility and chemicals & materials all link to the OFS story (a furniture manufacturer); robotics & automation, energy & infrastructure and advanced manufacturing link to Carbon Robotics. No industry page links to the Ultima Genomics story, and none shows a result number.Source
  • 14

    Two of Lumari's three stories run on NetSuite (Carbon Robotics and Ultima Genomics, which also uses Arena PLM). The blog has NetSuite, SAP and Dynamics 365 guides, but the site has no integrations pages at all. A NetSuite buyer can't find 'works with NetSuite, here are two customers' in one place.

    High impactMedium effort First result in 2 months Co founder

    First action

    Write the NetSuite fields Lumari writes back, from the Carbon Robotics and Ultima stories.

    How to measure it

    Integration-page demo bookings

    Now
    –
    Target
    8 a month
    By
    2 quarters

    Steps

    1. 1

      Write NetSuite

      Data flow, approvals, setup time, two stories.

      Co-founder (product and engineering) 1 week

    2. 2

      Build the template

      /integrations/<system> page type.

      Software Engineer 3 days

    3. 3

      Add a diagram

      Email to Lumari to ERP, with approval in Slack or Teams.

      Software Engineer 2 days

    4. 4

      Link guides

      Blog ERP guides to their pages.

      Software Engineer 1 day

    5. 5

      Add more ERPs

      SAP, Dynamics 365, Oracle, Arena.

      Co-founder (product and engineering) 1 month

    6. 6

      Target

      Outbound to manufacturers known to run NetSuite.

      Co-founder (go-to-market) ongoing

    First result
    2 months
    Cost
    Staff time
    Owner
    Co founder (product and engineering)

    Smallest test

    Publish the NetSuite page and use it in ten outbound emails.

    Why it works

    Create /integrations/netsuite first: what Lumari reads and writes (PO dates, split lines, tracking numbers), how approvals flow, setup time, and the two NetSuite stories. Then SAP, Dynamics 365, Oracle and Arena, each linking to its blog guide. Use the canonical list from idea 4.

    Mid-size manufacturers search and shortlist by ERP. A dedicated page with proof matches that intent, and NetSuite users are Lumari's proven sweet spot.

    Risks and how to handle them

    • Pages for thinly proven ERPs

      Mark the support level honestly.

    Builds on

    Evidence

    • Your websiteCarbon Robotics case study (agricultural robots; Gmail, NetSuite, Slack): before Lumari only 10–20% of open POs had a delivery date the team trusted, and keeping orders current could take more than half of each buyer's week. Results: "100% of open POs have trusted delivery dates", implementation "under 2 weeks", 24/7 open-order monitoring, "100% supplier adoption"; "We didn't know something was going to be late until it was late."Source
    • Your websiteUltima Genomics case study (sequencing systems; product BOMs of 3,000+ parts; NetSuite, Arena PLM, Outlook and Teams): "20×+ faster RFQ-to-PO processing", "99% fewer parts requiring team attention", "100% supplier adoption"; "Instead of focusing on thousands of parts, we're focusing on the 20 that have issues" (Director of Global Supply Chain).Source
    • Your websiteSitemap (69 URLs, checked November 9, 2026): homepage, contact, about, careers, security, privacy, terms, a glossary, 8 industry pages plus an index, 3 case studies and 44 blog posts; no pricing, integrations, calculator or comparison pages outside the blog.Source
    • Your websiteBlog: 44 posts from March 13 to August 17, 2026 (about two a week), none since August 17; categories Comparison, Guide, Insight, Operations and Automation; ERP guides for SAP, NetSuite and Dynamics 365; no newsletter signup, template download or calculator, only "Book a Demo".Source
  • 15

    LinkedIn is Lumari's only linked social channel, and the YC launch drew 128 upvotes. Procurement and supply chain leaders are on LinkedIn, and Lumari has vivid, specific numbers: 10–20% of open POs with trusted dates, "thousands of parts" down to "the 20 that have issues", three people's work done by one.

    Medium impactLow effort First result in 1 month Co founder

    First action

    Write the first post on the 10–20% trusted-dates baseline.

    How to measure it

    LinkedIn-sourced demos

    Now
    –
    Target
    5 a month
    By
    1 quarter

    Steps

    1. 1

      List 12 numbers

      From the three stories and the blog.

      Co-founder (go-to-market) 1 day

    2. 2

      Write in batches

      Four posts at a time.

      Co-founder (go-to-market) monthly

    3. 3

      Post weekly

      Both founders, different days.

      Co-founder (product and engineering) weekly

    4. 4

      Link offers

      Health check or calculator in the comments.

      Co-founder (go-to-market) weekly

    5. 5

      Engage

      Reply to every procurement commenter.

      Co-founder (go-to-market) daily

    6. 6

      Track

      Ask 'how did you hear' on every booking.

      Co-founder (go-to-market) ongoing

    First result
    1 month
    Cost
    $0
    Owner
    Co founder (go to market)

    Smallest test

    Four posts in four weeks; count profile visits and demos.

    Why it works

    Each founder posts once a week: one number, the story behind it, and what the buyer did differently, with the case study or calculator linked in a comment. Alternate with short posts on supplier behaviour (acknowledgement habits, quotes arriving as PDFs). Invite readers to the open-PO health check.

    Founder-led posts reach buyers at near zero cost, and concrete numbers outperform product announcements.

    Risks and how to handle them

    • Founder time

      Batch-write monthly; keep posts short.

    Evidence

    • Your websiteChannels: LinkedIn is the only social profile linked from the site; no YouTube, X or newsletter; lumari.io redirects permanently to lumari.ai.Source
    • Y Combinator launch"Lumari - AI Digital Workers for Supply Chain" (128 upvotes): agents run on existing ERP, email, Slack and Excel with no supplier onboarding; customers set guardrails and configure agents in plain English; customers range from "Fortune 500s" to fast-growing scale-ups.Source
    • Your websiteCarbon Robotics case study (agricultural robots; Gmail, NetSuite, Slack): before Lumari only 10–20% of open POs had a delivery date the team trusted, and keeping orders current could take more than half of each buyer's week. Results: "100% of open POs have trusted delivery dates", implementation "under 2 weeks", 24/7 open-order monitoring, "100% supplier adoption"; "We didn't know something was going to be late until it was late."Source
  • 16

    Every case study describes custom setup: Lumari Forge encodes each customer's approval paths, follow-up timing by commodity, and escalation rules. The new forward deployed engineer will work on the largest engagements with a team of five. Without templates, each new customer costs the same founder time, and the two-week go-live claim depends on heroics.

    High impactMedium effort First result in 1 quarter Founding Forward Deployed Eng…

    First action

    Write down the Carbon Robotics setup as the first template.

    How to measure it

    Days from kickoff to first live agent

    Now
    –
    Target
    7 days
    By
    2 quarters

    Steps

    1. 1

      Document three setups

      One per published customer.

      Founding Forward Deployed Engineer 2 weeks

    2. 2

      Strip customer data

      Keep only rules and structure.

      Founding Forward Deployed Engineer 1 week

    3. 3

      Add a template picker

      In onboarding.

      Software Engineer 2 weeks

    4. 4

      Start pilots from templates

      Every new customer.

      Founding Forward Deployed Engineer ongoing

    5. 5

      Measure

      Days to live, founder hours per customer.

      Co-founder (product and engineering) monthly

    6. 6

      Publish

      Day-one templates on industry pages.

      Software Engineer 1 week

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    Founding Forward Deployed Engineer

    Smallest test

    Start the next pilot from the Carbon Robotics template and time it.

    Why it works

    After each deployment, save the configuration as a starting template: 'NetSuite + Slack open-PO follow-up', 'RFQ from BOM with landed cost', 'MRP to delivery with PLM revisions'. Start new pilots from the closest template and measure days to first live agent. Show the templates on industry and integration pages as 'what you get on day one'.

    Templates cut onboarding time and founder hours per customer, protect the two-week promise and make the product easier to explain.

    Risks and how to handle them

    • Templates leak a customer's practices

      Keep only generic rules and get the customer's agreement.

    Evidence

    • HiringThree open roles on Y Combinator's job board, all in San Francisco, at a team of 5 founded in 2025: a Founding Forward Deployed Engineer ($110K–$170K, 0.25%–3.00% equity) who works with the founders on the largest customer engagements, turns customer workflows into implementations and builds production agents; a Software Engineer; and a "Former Founders" role spanning product, engineering, operations and go-to-market.Source
    • Your websiteOFS case study (furniture maker since 1937): before Lumari one RFQ took 1–2 days to prepare, comparing 10–15 line items took over 2 hours, and manual sourcing took 20–25 hours a week. Results: "10× faster RFQ processing", "2× faster landed-cost comparison", "2 weeks implementation", "100% supplier adoption"; "Without Lumari, it would have taken three people to do what one person was able to do by himself" (Sourcing Manager).Source
    • Your websiteCarbon Robotics case study (agricultural robots; Gmail, NetSuite, Slack): before Lumari only 10–20% of open POs had a delivery date the team trusted, and keeping orders current could take more than half of each buyer's week. Results: "100% of open POs have trusted delivery dates", implementation "under 2 weeks", 24/7 open-order monitoring, "100% supplier adoption"; "We didn't know something was going to be late until it was late."Source
  • 17

    Customers describe Lumari as doing "work that the team wasn't getting done before", which is invisible by nature. A VP of Supply Chain who renews or expands can't see the follow-ups sent, dates corrected or late orders caught unless someone counts them.

    Medium impactMedium effort First result in 2 months Co founder

    First action

    Pull last month's counts for one customer by hand.

    How to measure it

    Net revenue retention

    Now
    –
    Target
    120%+
    By
    4 quarters

    Steps

    1. 1

      Pick measures

      Six counts and one hours estimate.

      Co-founder (product and engineering) 2 days

    2. 2

      Build the query

      From agent activity logs.

      Software Engineer 1 week

    3. 3

      Design one page

      Forwardable PDF or email.

      Software Engineer 3 days

    4. 4

      Send monthly

      Champion and manager.

      Founding Forward Deployed Engineer monthly

    5. 5

      Use in renewals

      Twelve-month totals.

      Co-founder (go-to-market) per renewal

    6. 6

      Ask for stories

      When numbers are strong.

      Co-founder (go-to-market) quarterly

    First result
    2 months
    Cost
    Engineering time
    Owner
    Co founder (product and engineering)

    Smallest test

    Send a hand-made report to one customer and ask for feedback.

    Why it works

    Generate a monthly one-page report per customer: RFQs sent and returned, follow-ups sent, POs acknowledged, ERP dates updated, late shipments flagged early, estimated buyer hours saved (using the calculator's model). Send it to the champion and their manager, and use it in renewals and in asking for case studies.

    Making invisible work visible protects renewals, gives champions internal credit and creates the numbers for future stories.

    Risks and how to handle them

    • Hours estimates are challenged

      Show counts first and the estimate's assumptions second.

    Builds on

    Evidence

    • Your websiteCustomers page: three stories (OFS, furniture; Carbon Robotics, robotics; Ultima Genomics, life sciences), two "Coming soon" tiles for Electronics Manufacturing and Industrial Manufacturing, and 12 quotes credited by role only (such as "Director of Global Supply Chain" and "Sourcing Coordinator") with no company named.Source
    • Your websiteCarbon Robotics case study (agricultural robots; Gmail, NetSuite, Slack): before Lumari only 10–20% of open POs had a delivery date the team trusted, and keeping orders current could take more than half of each buyer's week. Results: "100% of open POs have trusted delivery dates", implementation "under 2 weeks", 24/7 open-order monitoring, "100% supplier adoption"; "We didn't know something was going to be late until it was late."Source
  • 18

    The three stories enter at different points: Carbon Robotics at open-PO follow-up, OFS at RFQs and landed cost, Ultima Genomics end to end from MRP to delivery. Lumari's edge over SourceDay is covering both sides, so each single-side customer is an obvious expansion.

    High impactLow effort First result in 1 quarter Co founder

    First action

    Map live workflows for every current customer.

    How to measure it

    Two-sided accounts

    Now
    –
    Target
    50% of customers
    By
    3 quarters

    Steps

    1. 1

      Map accounts

      Live workflows per customer.

      Co-founder (go-to-market) 1 day

    2. 2

      Find the gap

      Manual work on the other side, from the customer's own inbox volume.

      Founding Forward Deployed Engineer 1 week

    3. 3

      Write the offer

      30-day add-on with a success measure.

      Co-founder (go-to-market) 2 days

    4. 4

      Pitch

      In the monthly report review.

      Co-founder (go-to-market) monthly

    5. 5

      Deploy from template

      Use idea 16 templates.

      Founding Forward Deployed Engineer 2 weeks

    6. 6

      Track

      Expansion revenue per account.

      Co-founder (go-to-market) quarterly

    First result
    1 quarter
    Cost
    Staff time
    Owner
    Co founder (go to market)

    Smallest test

    Pitch one PO-side customer an RFQ add-on this month.

    Why it works

    For each customer, map which workflows are live. Propose the other side as a 30-day add-on using the customer's own data (for a PO-side customer: 'your buyers still compare quotes by hand; here are last month's RFQs'). Price expansion per workflow, and use Ultima as the end-to-end reference.

    Expansion is cheaper than new logos, and every expanded account becomes an end-to-end story.

    Risks and how to handle them

    • A different team owns the other side

      Ask the champion to introduce the sourcing or purchasing lead.

    Builds on

    Evidence

    • Your websiteCarbon Robotics case study (agricultural robots; Gmail, NetSuite, Slack): before Lumari only 10–20% of open POs had a delivery date the team trusted, and keeping orders current could take more than half of each buyer's week. Results: "100% of open POs have trusted delivery dates", implementation "under 2 weeks", 24/7 open-order monitoring, "100% supplier adoption"; "We didn't know something was going to be late until it was late."Source
    • Your websiteOFS case study (furniture maker since 1937): before Lumari one RFQ took 1–2 days to prepare, comparing 10–15 line items took over 2 hours, and manual sourcing took 20–25 hours a week. Results: "10× faster RFQ processing", "2× faster landed-cost comparison", "2 weeks implementation", "100% supplier adoption"; "Without Lumari, it would have taken three people to do what one person was able to do by himself" (Sourcing Manager).Source
    • Your websiteUltima Genomics case study (sequencing systems; product BOMs of 3,000+ parts; NetSuite, Arena PLM, Outlook and Teams): "20×+ faster RFQ-to-PO processing", "99% fewer parts requiring team attention", "100% supplier adoption"; "Instead of focusing on thousands of parts, we're focusing on the 20 that have issues" (Director of Global Supply Chain).Source
    • Your website"Lumari vs SourceDay" (updated April 22, 2026), the only head-to-head page: the text says teams "go live in days" while its own table lists Lumari's "Time to go live" as "Weeks"; it says Lumari "connects to SAP, Oracle, NetSuite, Epicor, and others" (Epicor is not in the homepage list).Source
  • 19

    Two of three customers run NetSuite, one with Arena PLM. Mid-size manufacturers usually adopt and extend these systems through implementation partners, who hear 'our buyers are drowning in supplier email' long before a software search starts. Lumari has no partner page or program today.

    Medium impactMedium effort First result in 1 quarter Co founder

    First action

    Ask Carbon Robotics and Ultima Genomics which consultants set up their NetSuite.

    How to measure it

    Pilots from partners

    Now
    –
    Target
    4
    By
    2 quarters

    Steps

    1. 1

      List partners

      From customers and partner directories.

      Co-founder (go-to-market) 1 week

    2. 2

      Write the brief

      What Lumari does in NetSuite, and the referral terms.

      Co-founder (go-to-market) 2 days

    3. 3

      Recruit five

      Intro calls.

      Co-founder (go-to-market) 1 month

    4. 4

      Train

      Thirty-minute demo and the health check.

      Founding Forward Deployed Engineer per partner

    5. 5

      Co-market

      One webinar each.

      Founding GTM hire (Former Founders role) quarterly

    6. 6

      Track

      Referrals to pilots.

      Co-founder (go-to-market) monthly

    First result
    1 quarter
    Cost
    Referral fees on closed deals
    Owner
    Co founder (go to market)

    Smallest test

    Sign one partner and run one joint health check.

    Why it works

    Recruit five NetSuite or PLM consultancies that serve manufacturers. Give them a one-page brief, the NetSuite page, a referral fee or co-delivery role, and the open-PO health check to offer clients. Run one joint webinar per partner with a shared customer story.

    Implementation partners bring trusted, well-timed introductions, and Lumari's write-back to the ERP makes their system look better.

    Risks and how to handle them

    • Partners refer poor-fit leads

      Share the ideal customer profile and the health-check criteria.

    Builds on

    Evidence

    • Your websiteCarbon Robotics case study (agricultural robots; Gmail, NetSuite, Slack): before Lumari only 10–20% of open POs had a delivery date the team trusted, and keeping orders current could take more than half of each buyer's week. Results: "100% of open POs have trusted delivery dates", implementation "under 2 weeks", 24/7 open-order monitoring, "100% supplier adoption"; "We didn't know something was going to be late until it was late."Source
    • Your websiteUltima Genomics case study (sequencing systems; product BOMs of 3,000+ parts; NetSuite, Arena PLM, Outlook and Teams): "20×+ faster RFQ-to-PO processing", "99% fewer parts requiring team attention", "100% supplier adoption"; "Instead of focusing on thousands of parts, we're focusing on the 20 that have issues" (Director of Global Supply Chain).Source
    • Your websiteSitemap (69 URLs, checked November 9, 2026): homepage, contact, about, careers, security, privacy, terms, a glossary, 8 industry pages plus an index, 3 case studies and 44 blog posts; no pricing, integrations, calculator or comparison pages outside the blog.Source

Big bets 3

Larger plays that can change the trajectory.

  • 20

    Lumari's agents send RFQs, chase acknowledgements and read every supplier reply. That makes it one of the few places that can measure how suppliers actually behave: how long acknowledgements take, how many follow-ups a quote needs, how often promised dates change. SourceDay already publishes a Supplier Reliability Index, but Lumari sees the RFQ side too, which a PO-only tool cannot.

    High impactHigh effort First result in 2 quarters Co founder

    First action

    Check customer contracts for aggregate-data rights and draft the five measures.

    How to measure it

    Benchmark-sourced demos

    Now
    –
    Target
    20 per edition
    By
    3 quarters

    Steps

    1. 1

      Confirm data rights

      Aggregate, anonymised use in contracts.

      Outside counsel 2 weeks

    2. 2

      Define measures

      Five, with clear definitions.

      Co-founder (product and engineering) 1 week

    3. 3

      Build the pipeline

      From agent logs, with minimum sample sizes.

      Software Engineer 1 month

    4. 4

      Write the report

      Findings by commodity, plus methodology.

      Founding GTM hire (Former Founders role) 1 month

    5. 5

      Launch

      LinkedIn, trade press, a webinar.

      Co-founder (go-to-market) 2 weeks

    6. 6

      Personalise

      Customer percentiles in monthly reports.

      Software Engineer 2 weeks

    7. 7

      Repeat

      Twice a year.

      Co-founder (product and engineering) 6 months

    First result
    2 quarters
    Cost
    Engineering and writing time; legal review
    Owner
    Co founder (product and engineering)

    Smallest test

    Publish one statistic (median follow-ups per quote) on LinkedIn.

    Why it works

    Aggregate anonymised data across customers: median time to RFQ reply, follow-ups per quote, acknowledgement rates, share of promised dates later revised, and quote formats (PDF, spreadsheet, email body). Publish twice a year by commodity and region, with a methodology note. Give customers their own percentile in the monthly report.

    Original data earns press, links and AI-assistant citations, and the benchmark becomes a reason for prospects to ask 'how do we compare?'

    Risks and how to handle them

    • Sample too small to be credible

      Publish only measures with enough data and state the sample size.

    • Customers object to data use

      Ask for opt-in and give participants an early copy.

    Builds on

    Evidence

    • Competitor researchRivals' own homepages: Didero, "Supply chains on autopilot" for manufacturers and distributors, with a "Run Your Numbers" ROI calculator and "18 days from ERP connect to first end-to-end automation"; SourceDay, "The #1 PO Management Solution for Manufacturers & Distributors", "123K suppliers activated", named customer results and a Supplier Reliability Index (Fall 2026) report; Traza, role-specific procurement agents with a long integrations list including Microsoft Dynamics, Coupa and Procore.Source
    • Your websiteHomepage: an "AI supply chain platform" for direct procurement (YC X25) with agents for RFQs, quote extraction, BOM processing, PO tracking, compliance data (country of origin, HS codes, RoHS, conflict minerals) and landed cost; suppliers keep replying by email with no portal; integrations listed as Gmail, SAP, NetSuite, Oracle, JDE, Vista and Procore, plus Slack and Microsoft Teams; the only call to action is "Book a Demo" and there is no pricing page.Source
    • Your websiteGlossary: "61 terms across 6 topics" (such as OTIF, EDI 855, promise date, landed cost and approved manufacturer list) on one page, each with a "Related guide" link to the blog; no page per term.Source
  • 21

    Lumari already collects country of origin, HS codes, RoHS, conflict-minerals data and certifications from suppliers, and its blog covers tariffs, nearshoring and customs enforcement. Chasing suppliers for these documents is the same email follow-up work Lumari automates, but today it is one line in a feature list, not something a compliance or trade lead can buy.

    High impactHigh effort First result in 2 quarters Co founder

    First action

    Ask current customers how many hours a month they spend collecting supplier compliance documents.

    How to measure it

    New logos entering through compliance

    Now
    –
    Target
    5
    By
    3 quarters

    Steps

    1. 1

      Validate demand

      Ten interviews with quality and trade leads.

      Co-founder (go-to-market) 1 month

    2. 2

      Define scope

      Fields, documents and write-back targets.

      Co-founder (product and engineering) 2 weeks

    3. 3

      Build the workflow

      Request, chase, extract, flag gaps.

      Software Engineer 6 weeks

    4. 4

      Launch the page

      Own landing page and pilot.

      Software Engineer 1 week

    5. 5

      Pilot

      Three customers.

      Founding Forward Deployed Engineer 1 month

    6. 6

      Cross-sell

      Offer PO follow-up on the same suppliers.

      Co-founder (go-to-market) ongoing

    First result
    2 quarters
    Cost
    One quarter of engineering focus
    Owner
    Co founder (product and engineering)

    Smallest test

    Run one compliance-document chase for an existing customer's top 50 suppliers.

    Why it works

    Package a 'Supplier compliance data' workflow: pick parts or suppliers, the agents request and chase the documents by email, extract the fields and flag gaps, and the results write back to the ERP or PLM. Offer it as an entry product for teams that are not ready to automate RFQs, with its own page, a pilot and a buyer persona (trade compliance or quality).

    It opens a second budget holder and a new entry point. Every compliance customer is a short step from PO follow-up on the same suppliers.

    Risks and how to handle them

    • Buyers expect legal assurance about the data

      Position it as collection and gap-flagging; the customer stays responsible for compliance decisions.

    • Distraction from the core product

      Reuse the existing request and extraction agents.

    Evidence

    • Your websiteHomepage: an "AI supply chain platform" for direct procurement (YC X25) with agents for RFQs, quote extraction, BOM processing, PO tracking, compliance data (country of origin, HS codes, RoHS, conflict minerals) and landed cost; suppliers keep replying by email with no portal; integrations listed as Gmail, SAP, NetSuite, Oracle, JDE, Vista and Procore, plus Slack and Microsoft Teams; the only call to action is "Book a Demo" and there is no pricing page.Source
    • Your websiteBlog: 44 posts from March 13 to August 17, 2026 (about two a week), none since August 17; categories Comparison, Guide, Insight, Operations and Automation; ERP guides for SAP, NetSuite and Dynamics 365; no newsletter signup, template download or calculator, only "Book a Demo".Source
  • 22

    The aerospace & defense page promises "Procurement built for programs that cannot drift" and talks about controlled documents, flow-downs and certifications, but it never mentions ITAR, CMMC, AS9100 or DFARS. Its only proof is a furniture manufacturer. Defense buyers screen on exactly those terms, so the page may attract leads that cannot buy yet, using founder time a five-person team does not have.

    Medium impactHigh effort First result in 1 quarter Co founder

    First action

    Count aerospace and defense leads from the last six months and where each one stalled.

    How to measure it

    A&D lead-to-pilot rate

    Now
    –
    Target
    Decision made and page updated
    By
    1 quarter

    Steps

    1. 1

      Review leads

      Volume and where each stalled.

      Co-founder (go-to-market) 1 day

    2. 2

      Get advice

      A specialist on controlled-data requirements.

      Co-founder (product and engineering) 1 month

    3. 3

      Cost the work

      Hosting, access controls, audits.

      Co-founder (product and engineering) 2 weeks

    4. 4

      Decide

      Invest, narrow or pause.

      Co-founder (go-to-market) 1 day

    5. 5

      Update the page

      Honest scope and real answers.

      Software Engineer 1 day

    6. 6

      Find a design partner

      If investing: one supplier.

      Co-founder (go-to-market) 1 quarter

    First result
    1 quarter
    Cost
    Advice fees; large if investing
    Owner
    Co founder (product and engineering)

    Smallest test

    Add one honest sentence on the current scope to the page this week.

    Why it works

    Make an explicit call. Either invest: get specialist advice on what controlled-data handling defense suppliers need, decide what Lumari will support, win one design-partner supplier and publish real answers on the page. Or narrow: retitle the page to commercial aerospace suppliers and remove defense language until the requirements are met. Review in two quarters.

    Focus wins early markets. A clear yes or no stops the page attracting deals that stall at security review, and a real yes opens a segment where few agent startups qualify.

    Risks and how to handle them

    • Pausing loses early demand

      Keep a waitlist for defense suppliers.

    Evidence

    • Your websiteAerospace & defense page: "Procurement built for programs that cannot drift", covering drawings, revisions, certifications, flow-downs and controlled documents with human sign-off; it does not mention ITAR, CMMC, AS9100 or DFARS.Source
    • Your websiteIndustry pages (8, checked November 9, 2026): each shows one quote credited by job title only and one "Read more" link. Aerospace & defense, semiconductors & electronics, life sciences & medical devices, automotive & mobility and chemicals & materials all link to the OFS story (a furniture manufacturer); robotics & automation, energy & infrastructure and advanced manufacturing link to Carbon Robotics. No industry page links to the Ultima Genomics story, and none shows a result number.Source
    • HiringThree open roles on Y Combinator's job board, all in San Francisco, at a team of 5 founded in 2025: a Founding Forward Deployed Engineer ($110K–$170K, 0.25%–3.00% equity) who works with the founders on the largest customer engagements, turns customer workflows into implementations and builds production agents; a Software Engineer; and a "Former Founders" role spanning product, engineering, operations and go-to-market.Source

Wildcards 3

Unexpected experiments, each with a cheap way to test it.

  • 23

    The glossary defines 61 procurement terms (OTIF, EDI 855, promise date, approved manufacturer list) on a single page with no URL per term. Buyers and AI assistants look up exactly these terms, and a single long page can only rank for a few of them.

    Medium impactMedium effort First result in 2 months Software Engineer

    First action

    Add a linkable anchor for each of the 61 terms today.

    How to measure it

    Glossary organic sessions

    Now
    –
    Target
    +100%
    By
    2 quarters

    Steps

    1. 1

      Add anchors

      One per term on the current page.

      Software Engineer 2 hours

    2. 2

      Pick 15 terms

      Closest to the product.

      Founding GTM hire (Former Founders role) 1 day

    3. 3

      Build the template

      Definition, example, measure, Lumari, guide.

      Software Engineer 3 days

    4. 4

      Write pages

      Three a week.

      Founding GTM hire (Former Founders role) 5 weeks

    5. 5

      Add structured data

      Definition markup on each page.

      Software Engineer 1 day

    6. 6

      Measure

      Search Console by page.

      Software Engineer monthly

    First result
    2 months
    Cost
    Writing time
    Owner
    Software Engineer

    Smallest test

    Publish five term pages and compare them with the glossary in two months.

    Why it works

    Pick the 15 terms closest to what Lumari automates (PO acknowledgement, promise date, open PO report, expediting, supplier response rate, landed cost). Give each its own short page: definition, a worked example, how teams measure it, how Lumari handles it, and the related guide. Keep the glossary page as the index, with an anchor for every term.

    Definition pages capture early-stage searches and are easy for AI assistants to quote, and each one links to proof and the calculator.

    Risks and how to handle them

    • Thin pages

      Only publish terms with a real worked example.

    Evidence

    • Your websiteGlossary: "61 terms across 6 topics" (such as OTIF, EDI 855, promise date, landed cost and approved manufacturer list) on one page, each with a "Related guide" link to the blog; no page per term.Source
    • Google PageSpeedHomepage scores 99 on mobile and desktop, accessibility 97 (one colour-contrast issue), SEO 100; real visitors pass Core Web Vitals (LCP 881 ms, INP 62 ms, CLS 0), and LCP is 31% faster than in the previous period.Source
  • 24

    Every Lumari customer reaches dozens or hundreds of suppliers by email, and all three stories report 100% supplier adoption because suppliers change nothing. Many of those suppliers are manufacturers themselves, chasing their own vendors for quotes and dates. They see well-run RFQs and follow-ups every week without knowing who runs them.

    Medium impactLow effort First result in 2 quarters Co founder

    First action

    Ask two customers whether they would allow an optional footer on agent emails.

    How to measure it

    Supplier-sourced pilots

    Now
    –
    Target
    3
    By
    3 quarters

    Steps

    1. 1

      Ask customers

      Opt-in footer and a referral credit.

      Co-founder (go-to-market) 2 weeks

    2. 2

      Write the footer

      One neutral line.

      Co-founder (go-to-market) 1 hour

    3. 3

      Build the supplier page

      Nothing changes for you, and how it works for buyers.

      Software Engineer 3 days

    4. 4

      Add a setting

      Footer on or off per customer.

      Software Engineer 2 days

    5. 5

      Track visits

      Supplier page to demo.

      Software Engineer ongoing

    6. 6

      Reward

      Credit the customer on a closed deal.

      Co-founder (go-to-market) per deal

    First result
    2 quarters
    Cost
    Referral credits
    Owner
    Co founder (go to market)

    Smallest test

    Turn the footer on for one consenting customer for a month.

    Why it works

    With each customer's consent, add an optional one-line footer to agent-sent emails ('Coordinated with Lumari: suppliers reply as usual') linking to a page for suppliers that explains nothing changes for them and invites them to see how their own purchasing could work the same way. Offer the referring customer a credit when a supplier becomes a customer.

    It turns the product's own emails into a network effect, aimed at a warm audience that has already seen it work.

    Risks and how to handle them

    • Customers want to stay invisible

      Off by default, opt-in only.

    Evidence

    • Your websiteHomepage: an "AI supply chain platform" for direct procurement (YC X25) with agents for RFQs, quote extraction, BOM processing, PO tracking, compliance data (country of origin, HS codes, RoHS, conflict minerals) and landed cost; suppliers keep replying by email with no portal; integrations listed as Gmail, SAP, NetSuite, Oracle, JDE, Vista and Procore, plus Slack and Microsoft Teams; the only call to action is "Book a Demo" and there is no pricing page.Source
    • Your websiteUltima Genomics case study (sequencing systems; product BOMs of 3,000+ parts; NetSuite, Arena PLM, Outlook and Teams): "20×+ faster RFQ-to-PO processing", "99% fewer parts requiring team attention", "100% supplier adoption"; "Instead of focusing on thousands of parts, we're focusing on the 20 that have issues" (Director of Global Supply Chain).Source
    • Your websiteOFS case study (furniture maker since 1937): before Lumari one RFQ took 1–2 days to prepare, comparing 10–15 line items took over 2 hours, and manual sourcing took 20–25 hours a week. Results: "10× faster RFQ processing", "2× faster landed-cost comparison", "2 weeks implementation", "100% supplier adoption"; "Without Lumari, it would have taken three people to do what one person was able to do by himself" (Sourcing Manager).Source
  • 25

    Lumari already has a guide on procurement software for contract manufacturers and lists contract-manufacturer operations as a use case. Contract manufacturers buy direct materials for many OEM customers at once, with constant RFQs on new BOMs, so they feel the RFQ and follow-up load more than almost anyone.

    Medium impactMedium effort First result in 1 quarter Co founder

    First action

    Turn the contract-manufacturer guide into a landing page with a calculator link.

    How to measure it

    CM pilots started

    Now
    –
    Target
    3
    By
    2 quarters

    Steps

    1. 1

      Build the list

      30 contract manufacturers in target sectors.

      Co-founder (go-to-market) 1 week

    2. 2

      Publish the page

      Quote speed for new programs.

      Software Engineer 1 week

    3. 3

      Write outreach

      Founder emails with the BOM-to-RFQ angle.

      Co-founder (go-to-market) 3 days

    4. 4

      Offer the RFQ sprint

      The pilot from idea 9 on one new program.

      Founding Forward Deployed Engineer per pilot

    5. 5

      Measure

      Quote turnaround before and after.

      Founding Forward Deployed Engineer per pilot

    6. 6

      Publish

      A contract-manufacturer story.

      Founding GTM hire (Former Founders role) 1 quarter

    First result
    1 quarter
    Cost
    Staff time
    Owner
    Co founder (go to market)

    Smallest test

    Email ten contract manufacturers with the quote-speed angle.

    Why it works

    Run a focused push on 30 mid-size contract manufacturers in electronics and medical devices: a dedicated page (quote turnaround for new programs, BOM-to-RFQ in hours), the RFQ calculator, and the OFS and Ultima numbers on BOM-heavy sourcing. Pitch quote speed as a way to win more OEM programs, not only as cost saving.

    For a contract manufacturer, faster quotes mean more won business, which is an easier budget than efficiency.

    Risks and how to handle them

    • OEM confidentiality limits data access

      Start with one program and clear data rules.

    Builds on

    Evidence

    • Your websiteSitemap (69 URLs, checked November 9, 2026): homepage, contact, about, careers, security, privacy, terms, a glossary, 8 industry pages plus an index, 3 case studies and 44 blog posts; no pricing, integrations, calculator or comparison pages outside the blog.Source
    • Your websiteOFS case study (furniture maker since 1937): before Lumari one RFQ took 1–2 days to prepare, comparing 10–15 line items took over 2 hours, and manual sourcing took 20–25 hours a week. Results: "10× faster RFQ processing", "2× faster landed-cost comparison", "2 weeks implementation", "100% supplier adoption"; "Without Lumari, it would have taken three people to do what one person was able to do by himself" (Sourcing Manager).Source
    • Your websiteUltima Genomics case study (sequencing systems; product BOMs of 3,000+ parts; NetSuite, Arena PLM, Outlook and Teams): "20×+ faster RFQ-to-PO processing", "99% fewer parts requiring team attention", "100% supplier adoption"; "Instead of focusing on thousands of parts, we're focusing on the 20 that have issues" (Director of Global Supply Chain).Source
More example playbooks and reviews

More growth playbooks

Other companies we have researched, each read from what they are hiring for.

  • Cresta growth strategyAn AI platform for customer experience: autonomous AI Agents, real-time Agentic Assist for human agents, Deputy Agent for back-office…21 growth ideas
  • Arch growth strategySoftware and services that collect, extract and verify private investment documents and data (statements, capital calls, K-1s), with…22 growth ideas
  • mgsh. growth strategyA London-based boutique GTM engineering consultancy and Clay Solutions Partner. It cleans and enriches CRMs, builds qualification, scoring…23 growth ideas
  • Une Femme Wines growth strategyA women-founded California wine brand that sells sparkling and still wines in 250mL cans, 750mL bottles and reusable kegs. It calls itself…22 growth ideas
  • Feastables growth strategyThe MrBeast snack brand: chocolate bars, peanut butter and hazelnut cups, sour gummies and chocolate milk, made with 100% Fairtrade cocoa…21 growth ideas
  • Vestwell growth strategyA workplace savings platform: 401(k), 403(b), Solo(k) and pooled plans, plus emergency savings, student loan repayment, 529 education…23 growth ideas
  • Red Ventures growth strategyA portfolio of digital businesses (Bankrate, The Points Guy, Allconnect, Lonely Planet, RV EDU, Sage Home Loans) and client services…21 growth ideas
  • OpenWork growth strategyA free, open-source desktop AI agent app for macOS, Windows and Linux that works with any model, local models or your own keys, plus…23 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on November 10, 2026, and cites them throughout. Lumari did not commission, review or endorse it, and Programmable is not affiliated with Lumari. Company and product names are trademarks of their owners, used only to identify them. The ideas are suggestions and opinion, not professional, legal or financial advice, and not statements about how Lumari runs its business.

Something wrong, or do you represent Lumari? Email [email protected] and we will correct it or take it down.

30/60/90 roadmap

What to focus on in each month, and the ideas that carry it.

  1. Days 1 to 306 ideas

    Fix the proof and claims on pages buyers already see: industry pages, quotes, the demo page, the integration list, go-live wording and a trust page.

  2. Days 31 to 609 ideas

    Give buyers a reason to start: the hours calculator, the open-PO health check, a two-week pilot, head-to-head pages, a restarted blog with a capture offer, the two missing stories, ERP pages and a founder LinkedIn series.

  3. Days 61 to 9010 ideas

    Scale delivery and expansion (deployment templates, work-done reports, PO-to-RFQ expansion, ERP partners), commit to the big bets (supplier benchmark, compliance-data wedge, the aerospace decision) and test the wildcards.

The research behind the plan

3 research areas, each summarised in a few lines. Open any of them for the full detail.

Customers

What customers say

Customers value suppliers keep using email, Excel and PDFs, so adoption is 100%. The most cited problem: hours a week chasing suppliers for acknowledgements and dates.

  • Delivery dates they can trust, and knowing early when something will be late
  • Quotes arriving as PDFs, spreadsheets and emails that must be retyped
  • In their words: “chasing suppliers”

Market

Competitive landscape

5 competitors compared: Didero, SourceDay, Traza, LightSource and 1 more.

  • Gap to exploit: Proof by industry and by ERP for mid-size manufacturers
  • Didero: Few named customer results on its homepage
  • SourceDay: Starts after the PO; no RFQ or quote comparison

Hiring signals

Lumari is a team of five hiring for delivery and range, not a sales team.

  • Founding Forward Deployed Engineer: Works with the founders on the largest customer engagements. Ideas 8, 9, 16.
  • Software Engineer: End-to-end product and site work. Ideas 1, 7, 14.
  • Former Founders: Ownership across product, operations and go-to-market. Ideas 11, 12, 20.

From the team that wrote this playbook

All products
  • ProgrammableAgencyWorking AI systems in days, not quarters (opens programmable.agency in a new tab)
  • ProgrammableInfoAn agent that finds, researches and asks firstNew accounts get 100,000 free enrichment credits with code BETA100K (opens programmable.info in a new tab)
  • ProgrammableDigitalScreenshots in, an animated product demo out (opens programmable.digital in a new tab)
  • ProgrammableWatchKnow the day a supplier falls out of compliance (opens programmable.watch in a new tab)
  • ProgrammableTalkGet registrants for your events, and know who’s coming (opens programmable.talk in a new tab)
  • ProgrammableMediaAn AI note taker, interpreter and webinar host for your calls (opens programmable.media in a new tab)
  • ProgrammablePageText what you need, your customer gets a page that works (opens programmable.page in a new tab)
  • ProgrammableCommunityForums with labelled AI members, never empty (opens programmable.community in a new tab)
ProgrammableMarketing
ExamplesLeaderboardsProductsTermsPrivacyCookiesDPALegalContact

© 2026 AI-Powered Growth Intelligence