1/ We audited our own AI last week by reading every fact it had pulled about three of a pilot partner's customers, record by record, and judging each one by hand.
If you're building anything that extracts facts from calls, Slack or tickets, here's the checklist we'd hand you after doing it 👇
1
2
99
6/ Let later events close earlier ones. When a customer declines, thirty open items can die with one sentence, and comparing facts two at a time will never catch it.
1
10
for every 1000 dollars of token spend, im gonna buy 1 share of $ant
2
106
Deployment teams feel this worse than anyone. Half of what a customer asks for gets said once, in a Slack thread or on a call, and by the time someone builds it the thread is 400 messages deep and the person who heard it has moved to another account.
We stopped expecting people to keep up with the channel and built OpenScaffold to read it for them, so every ticket shows up with what the customer actually said and when they said it. If you’re looking for a solution, DM me!
nitter.cf/scottastevenson/status…
Slack is seriously not working as a communication channel for companies working at AI speed
It blows out everyone's context window
As a founder working 80 hrs/week, who ruthlessly tracks my "actions per minute", I can barely stay on top
How can you expect anyone else to keep up?
We need more context isolation, smarter routing
What is the solution?
1
2
89
It took nine PRs to fix the things our product was getting wrong about our customers.
Before making any changes, we sat down and read through OpenScaffold from a customer's lens. The home screen told us to follow up on a kickoff the customer had already declined. A meeting that happened on Tuesday was still under “Next.” One change to a customer’s requirements showed up five separate times, each one presented as news.
The extraction was mostly right, but it couldn’t carry over.
We rebuilt how the harness holds a customer. Each customer now has one harness, and everyone on the team sees the same one. When a customer changes their mind, their latest statement replaces the earlier one, so it doesn’t show up as a conflict. When someone says “we will not be moving forward,” that sentence closes every open item it applies to. That last part is still behind a flag while we test it.
It turns out that our AI was doing its job. Teaching it to remember what came next is what fixed the bug. Now, our customers are able to see where their customers stand instantly.
Param Mehta retweeted
2 weeks before we planned to start fundraising, @ParamMehta24 and I pivoted to OpenScaffold.
Since then, we’ve closed 3x as many customers, and our ACV has increased 5x.
Here’s our story:
Param Mehta retweeted
Over the past week, I’ve been overwhelmed by the love and support of friends, industry colleagues, and people I've never met. Thank you to everyone who has shown kindness to my family and me. It means the world to me.
I came to the United States 53 years ago, and becoming an American citizen is one of the greatest gifts and proudest moments of my life. NVIDIA has been my life’s work. Building it into the company it is today alongside my colleagues has been a privilege and an honor. Nowhere but in America could a company like NVIDIA be possible. I love our country, and I love NVIDIA.
I did not live up to the standards expected of everyone at NVIDIA, and I have made serious mistakes in my personal life. I created problems for the Board that I deeply regret. I own my mistakes completely, and I am committed to cooperating with the Board’s independent investigation.
Since my departure, I’ve seen an outpouring of calls from NVIDIA’s employees, investors, business partners, and customers for me to return as CEO. Many continue to reach out to me directly as the company navigates complex technology, market, competitive, and geopolitical dynamics. NVIDIA is a once-in-a-generation company. If the Board of Directors decides that my return is in the best interest of our shareholders, our employees, the company, and America, I would be honored to answer these calls and return as CEO.
Thank you again to everyone who has shared their good wishes. I am profoundly humbled by your support. To my family: I love you, and I will spend the rest of my life being worthy of yours.
Jensen
Param Mehta retweeted
Replying to @ParamMehta24
@ParamMehta24 and I built OpenScaffold (YC F26) to help deployment teams get customers live faster by turning past deployments and scattered customer context into reusable playbooks.
Over the past 3 years, the number of AI deployments has increased by 4,600%, with demand projected to grow at an even faster pace.
Today, deployment teams are struggling to keep up with this demand. Critical customer context is scattered across GitHub, support tickets, and meeting recordings, slowing down every deployment.
OpenScaffold brings this information together into continuously updating models of each customer. When you need to ship a feature, resolve a bug, or get up to speed on an existing customer, OpenScaffold retrieves the relevant customer-specific context. Then, it’s passed to your coding agents and turns what worked into reusable playbooks.
Param and I met while working as employees #1 and #3 at Usul (YC S24), one of the fastest-growing defense tech companies in SF. We led deployments for some of the largest U.S. government contractors and helped grow the company’s revenue 10x in under a year.
If you’re looking to get customers live faster and make every deployment easier, grab a time with me here: calendar.app.google/pt8rrJW5…
Param Mehta retweeted
Steph Curry calls out Nick Young, Gilbert Arenas, and everyone else talking about Ayesha Curry, telling them to keep his wife’s name out of their mouths 😳
“Kind of speaks to a bigger conversation on how you view women in this world and what they’re allowed and what they’re not allowed to do.”











