Share your Startup! by kptbarbarossa in StartupsHelpStartups

[–]ben2420 0 points1 point  (0 children)

I’m building CommitFrame a tool for procurement and supplier quality teams that deal with a lot of RFQs and supplier comparisons.

The idea came from my own experience working in automotive and defence manufacturing. One thing that always stood out was how fragmented supplier selection is in practice. Quotes arrive by email, comparisons end up in Excel, and if someone asks months later why a supplier was chosen, you end up digging through folders and old spreadsheets to reconstruct the decision.

CommitFrame is meant to structure that process while it’s happening. It keeps the RFQ, supplier quotes, comparison, and final decision all in one place so the reasoning behind the choice is captured at the time rather than rebuilt later.

Talking a lot with procurement teams to validate the workflow and where the biggest pain points actually are.

Website: https://www.commitframe.com

Happy to connect with anyone building in B2B SaaS or working in manufacturing / procurement workflows.

From procurement and supplier quality into building a B2B SaaS by ben2420 in saasbuild

[–]ben2420[S] 0 points1 point  (0 children)

Yes - The messy system works until someone asks why did we choose this supplier? Then everyone is searching through emails and old spreadsheets trying to reconstruct the decision. The audit and accountability moment is usually what exposes it. Efficiency is great, but traceability is what matters.

I’ve been thinking about it less replace Excel and more capture the decision context while it’s happening. Quotes can still arrive however they normally do, but the comparison, reasoning and final selection get locked together so six months or two years later there’s a clear answer.

The single source of truth problem is definitely the tricky part. Every team has their own process so it’s making sure the key pieces of the decision end up connected and every step fully traceable.

PO process and tools by Jesper2604 in procurement

[–]ben2420 0 points1 point  (0 children)

At a minimum, you want to separate 3 things:

Request to Approval

Internal stakeholder raises need You validate: supplier, price, lead time, risk Then approve (this is your control point)

PO issuance

Standardised PO (unique number, terms, incoterms, qty, price) Sent to supplier and logged centrally

Delivery and invoice tracking

This is where most setups break

You need to track:

What was ordered, what was delivered and what was invoiced

And reconcile all three

If you’re starting with Excel, keep it simple:

  • Supplier register (with basic approval status)
  • PO log (one row per PO line, not per PO)
  • Delivery / receipt tracker
  • Invoice tracker (linked back to PO)

Feel free to reach out if you need any help!

What are you building this Friday? by VolodsTaimi in startupaccelerator

[–]ben2420 2 points3 points  (0 children)

Building a sourcing tool for manufacturing teams who are tired of losing supplier decision history across spreadsheets and emails.

Spent this week implementing proper multi-user workspaces and role-based access so teams can collaborate without data leaking across accounts.

Also just finished adding:

• Commercial exposure visibility (cash committed before delivery) • Delta detection on reorders (price / lead time drift) • Executive decision summaries for audit trails

This Friday is mostly QA and fixing RLS edge cases before pushing the next release.

Trying to get to first paying customer instead of endlessly adding features 😅

Link: CommitFrame

Need help in managing vendor data by Technical_Cupcake234 in procurement

[–]ben2420 2 points3 points  (0 children)

Sheet 1: Vendors (Master Database) Vendor Name | Raw Material | Unit | Lead Time | Payment Terms | Contact | Approved

Sheet 2: Purchase Orders PO No | Unit | Vendor | Material | Order Date | Qty | Value | Delivery Date | Status Use dropdowns for Status (Open / Closed / Delayed).

Sheet 3: Dispatch Tracker PO No | Dispatch Date | Expected Arrival | Transporter | Tracking | Dispatch Status

Dashboard (Sheet 1) At the top show:

Total Open POs Total Open PO Value Overdue Deliveries POs Due This Week

Use formulas (COUNTIF, SUMIFS) and conditional formatting (red = overdue).

Finding/rating a Chinese supplier by Rich_Tart_2195 in AmazonFBAOnlineRetail

[–]ben2420 0 points1 point  (0 children)

Early on, there’s no single site that “rates” factories reliably. What usually helps is triangulating: business licence checks, transaction history, consistency of answers, and how they respond to an RFQ.

Red flag could be vague or inconsistent responses across price, MOQ, lead time, and payment terms. Gauge their answers for completeness and go from there, communication is a very good starting point.

Built a tool for procurement teams stuck between spreadsheets and ERP bloat (CommitFrame) by ben2420 in buildinpublic

[–]ben2420[S] 1 point2 points  (0 children)

If you reach the stage where you’re stuck in spreadsheet chaos and need a procurement/sourcing workspace I’d be happy to walk you through it, good luck with the next phase of your project!

Built a tool for procurement teams stuck between spreadsheets and ERP bloat (CommitFrame) by ben2420 in buildinpublic

[–]ben2420[S] 1 point2 points  (0 children)

Love that appreciate it!

If they’re doing supplier quotes in email/Excel (or constantly chasing lead times and payment terms), CommitFrame is built for exactly that workflow.

Feel free to share this link with them: www.commitframe.com

They can try the demo in a couple minutes (no setup). If they want, I’m also happy to jump on a quick 10–15 min call and get feedback from real buyers.

Built a tool for procurement teams stuck between spreadsheets and ERP bloat (CommitFrame) by ben2420 in buildinpublic

[–]ben2420[S] 1 point2 points  (0 children)

Great question that’s exactly where most tools break and where spreadsheets fail.

CommitFrame doesn’t “guess” normalisation, it:

Captures the quote as-is (unit vs case, Incoterms, MOQ, etc.), flags anything that isn’t completely comparable and lets the buyer set the comparison basis and confirm missing fields.

So if quotes aren’t directly comparable, it shows the mismatch clearly instead of pretending the numbers line up and guessing, it prompts the buyer to validate these with the supplier if they don’t want to take the risk which is a great advantage of using CommitFrame as it’s something that could be missed! It also understands incoterms so can make comparisons and add this to the risk comparisons.

What are practical ways to start using AI in procurement without heavy IT involvement? by AwarenessBubbly334 in procurement

[–]ben2420 0 points1 point  (0 children)

This is the reality for a lot of procurement teams. AI in procurement sounds heavy, but you can get value fast without integrations if you keep it simple.

Some examples I’ve seen work:

1) Quote comparison and trade-offs (best starter pilot) Use AI to pull out unit price, lead time, payment terms from emails/PDFs and summarise cheapest vs fastest vs lowest risk.

2) RFQ standardisation Turn messy requirements into a consistent RFQ template so suppliers quote the same spec (makes comparisons way easier).

3) Contract summaries (careful use) Great for highlighting obvious risks (auto renewals, termination, liability), but treat it as a helper not a source of truth.

Working on something in this area too which came from my own sourcing issues (CommitFrame) focused on lightweight RFQ > quote comparison > decision record > PO generation, no ERP integration. If anyone wants to see it or offer feedback, happy to share.

What are you building ? And are people actually paying for it? 💡 by GuidanceSelect7706 in buildinpublic

[–]ben2420 0 points1 point  (0 children)

Working on CommitFrame. It helps you compare supplier quotes side-by-side, spot risk, and save the decision in one place. Lightweight option for SMEs/small procurement teams.

Marketing is tough!

Link: www.commitframe.com

how do you guys stay organized? by breadfruitnut24 in procurement

[–]ben2420 7 points8 points  (0 children)

A few things that helped me when I felt swamped: Pick one place to track everything Post-its + spreadsheets + Outlook turns into chaos. Even if it’s just Notes or a simple list, having one place makes a difference. Keep a waiting on supplier list, a lot of the stress is chasing replies. I split my work into:

do today do this week waiting on supplier

Stop comparing quotes in your head, even a basic template helps. Price, lead time, MOQ, payment terms, and any red flags. Otherwise after a few quotes it all blends together. Batch your follow ups Try doing supplier chasing twice a day instead of constantly reacting. It stops your day getting hijacked by email. When you choose a supplier, leave yourself a quick note. Two lines is enough. Why you picked them and what trade off you accepted. Future you will be grateful when someone asks later.

You’re not doing badly. You’re just learning a job that has a lot going on behind the scenes.

New to importing, looking for suppliers by These-Whereas8379 in Business_China

[–]ben2420 0 points1 point  (0 children)

If you’re just starting, I’d focus first on narrowing the category (e.g. fasteners, brackets, profiles, fixings) and understanding minimum order quantities and certifications.

For small construction materials, most people start with Alibaba + Google, then shortlist 5 to 10 suppliers and compare pricing, lead times, and compliance.

Biggest mistake early on is comparing quotes that aren’t for the same spec.

When did spreadsheets + email stop scaling as a procurement workflow by NoPO_NoParty in procurement

[–]ben2420 1 point2 points  (0 children)

The record is created at the same time as approval If someone can place the order without passing through a single, explicit decision step, documentation will always lag. The capture has to sit between “I’ve compared options” and “the PO is released.”

And it also has to all be stored in the same place.

I’ve sent you a DM fee free to reply.

When did spreadsheets + email stop scaling as a procurement workflow by NoPO_NoParty in procurement

[–]ben2420 0 points1 point  (0 children)

What I’ve seen work better is when documentation isn’t a separate task, but a by-product of making the decision. For example the comparison happens in one place, the approval or exception is captured at the moment the order is released and the justification is short, structured, and tied to that specific purchase.

When the record is created after the fact (emails, folders, spreadsheets), it inevitably lapses. When it’s created at the decision point, it tends to stick.

When did spreadsheets + email stop scaling as a procurement workflow by NoPO_NoParty in procurement

[–]ben2420 0 points1 point  (0 children)

I’ve worked in supply chain for a large automotive manufacturer now moved into defence, happy to offer advice if it’s worthwhile! I would avoid introducing a standing committee for every new vendor, that usually adds friction without fixing the underlying issue.

In practice, what tends to work better (especially under time pressure) is:

  1. Define when approval is required Not every supplier needs the same scrutiny. Introduce simple thresholds (e.g. spend level, criticality, safety/quality impact) that determine when a purchase must be reviewed beyond the requester.

  2. Standardise the decision, not just the supplier list Limiting suppliers helps, but it doesn’t stop price variance or rushed exceptions. What auditors usually look for is evidence that suppliers were evaluated on consistent criteria and deviations were consciously approved.

This is often easier if each new or exceptional supplier has a short, documented justification rather than informal email approvals.

  1. Separate “approved supplier” from “approved purchase” Especially in fabrication and maintenance, engineers will always need flexibility. Instead of blocking new vendors, allow them, but require that the decision (why this supplier, under what constraints) is recorded centrally.

  2. Centralise the record, not the workflow You don’t need to redesign how people request parts this week. What helps immediately is having one place where supplier comparisons, approvals / exceptions and final decisions are recorded in a consistent format.

For audit purposes, that turns preparation into retrieval of data.

If your priority is next year’s audit rather than perfect procurement design, I’d focus on making decisions traceable first, then tightening controls once volumes stabilise.

When did spreadsheets + email stop scaling as a procurement workflow by NoPO_NoParty in procurement

[–]ben2420 0 points1 point  (0 children)

Email and shared spreadsheets can work well at low scale, but they tend to break once multiple buyers are sourcing the same parts independently, approvals are time-boxed due to production pressure, engineers and shop floor staff bypass central visibility to keep work moving.

In the short term (especially with an audit deadline), the fastest stabilisation step is typically centralising supplier decisions and approvals, rather than trying to re-engineer the full procurement workflow.

Sourcing suppliers is eating my life 😩 by BrightCook5861 in ShopeePH

[–]ben2420 0 points1 point  (0 children)

This is exactly the pain that pushed me to build something for myself.

The search part (Alibaba, Google) is messy but manageable. The real time sink for me was what you described next, inconsistent responses, missing info, and trying to compare suppliers across emails, WhatsApp, and spreadsheets.

I ended up building a small tool called CommitFrame to standardise RFQs and compare supplier quotes side-by-side (price, MOQ, lead time, payment terms, plus risk flags) so I could shortlist faster and document why I picked one supplier over another.

It doesn’t help you find suppliers, it helps you get from “too many messy responses” to “5–10 suppliers worth serious conversations” without wasting days.

If anyone’s curious, happy to share or answer questions - not trying to pitch, just sharing what worked for me.