Looking for pilot users!
I've been building Theo over the past few weeks and am looking for a few small businesses to pilot it free.
The problem:
Every company loses years of institutional knowledge when key people leave. It's already in your Slack threads, emails, Google Drive, Docs, etc. It's just not organized or searchable.
What Theo does:
Connects to your Slack, Gmail, Google Drive, etc. reads everything, and turns it into a knowledge base anyone on the team can search in plain English. Ask "who handles vendor contracts?" or "what's the refund process?" and get a cited answer pulled from your company's own data. No documentation to write. No wikis to maintain.
The traction so far:
Posted about the problem on Reddit yesterday — 38k views and 140+ comments in 8 hours organically. The problem clearly resonates.
Looking for:
5 small businesses (10-200 employees) using Slack and Google Drive to pilot it free in exchange for honest feedback.
Live at meettheo.vercel.app
Happy to answer any questions — would love feedback from other builders too.
One thing I found interesting is that a lot of institutional knowledge problems look like search problems from the outside.
But sometimes the information isn't actually lost.
People just don't trust themselves to act on what they find without the person who originally held the context.
Those can end up being very different problems to solve.
I'd be curious what the Reddit responses made you believe about that distinction.
sorry for the very long response
I just went to look back at the Reddit post but turns ourt it was deleted due to someone spamming links, however, the Reddit responses leaned heavily toward the search problem, 'I can never find anything,' 'it's all buried in Slack.' But the comments that made the distinction were from people who said they knew who to ask, they just didn't want to bother that person again or felt like they should already know the answer. That's closer to what you're describing. The knowledge exists, the path to it exists, but the social friction stops people from using it.
So honestly the responses made me think the two problems are more entangled than they look. Search friction and trust friction often sit on top of each other. Theo tackles the search side directly, and every answer links back to the original doc, Slack thread, email, wherever it was, which I think helps with the trust side too. If you can see exactly where something came from and click through to it, you're more likely to act on it than if it's just an answer floating without context.
So while what you say is absolutely true, if the knowledge is found and cited, it become much easier for employees to overcome that issue.
That's the part I'd find most interesting.
Not whether search friction and trust friction overlap.
Whether solving one causes founders to overestimate how much of the other has actually been removed.
I've seen products create a lot more confidence in finding answers than confidence in acting on them.
Those don't always move together.
That's what Theo fixes. If you are or know anyone running a company that could use this, we're looking for pilot users. Free for a bit for pilots to get everything figured out and some feedback. Let me know!
Possibly.
The reason I asked is that I've seen teams become much better at locating information without becoming equally confident about what should happen next.
Those can look like the same problem from a distance.
That's where I'd be most curious to see what pilot users actually do.
If you would like to pilot with us, I'd be happy to set something up.
If not, do you know of anyone who may?
Possibly.
The reason I kept pushing on it is that I've seen products solve one layer of a problem so effectively that founders start attributing improvements in adjacent layers to the same thing.
Sometimes that's exactly what's happening.
Sometimes it isn't.
That's probably the part I'd be most interested in exploring further.
Happy to continue by email if useful.
Would love to continue by email. You can reach me at gfsimo90@gmail.com
Appreciate it.
Just sent something over.
Curious what the pilot users end up teaching you.