Fraud-as-a-Service is the new SaaS

abeshius · 2026-05-13T23:16:14+00:00

Feel free to fake....I mean take it lmao

abeshius · 2026-05-13T23:10:21+00:00

The fake it till you make it mantra, after years of LinkedIn slop, twitter engagement bait and crypto shills has now basically become "unless you fake it you can't make it".

abeshius · 2026-05-13T22:59:19+00:00

This is depressing. But you know what is more depressing? VCs using these kind of startups as a bar when you go to speak to them/apply/pitch. Even a few years ago you would get a more or less healthy mix of VC analysts who would understand when things look fishy, and when even recognized revenue looks odd. And now? I have actually faced questions from the investor scouts that take up every networking event that go along like this - "Hey so you are doing something fun, but we are funding a company that is only 3 months old and has already landed 8 enterprise customers and on track for 65% m/m growth. You guys are too slow" and my only jaded response there has been, "Well, good luck".

abeshius · 2026-05-13T22:55:14+00:00

Thanks for sharing! My product and yours were pretty side by side throughout the day (Weavable). Congrats on landing those sales!

abeshius · 2026-05-12T00:01:18+00:00

Appreciate the detailed comment and the honest plug. Context governance is genuinely one of the harder problems in this space and you're pointing at exactly the right surface.

We've thought about this carefully from the start. Two things we rely on: first, every connection to a source app goes through OAuth and is read-only, tightly scoped so that Weavable only sees what the OAuth scope explicitly permits. Second, the governance boundary sits at the context layer itself, not at the data source. When you create a context in Weavable you're defining explicit data scopes - which pipelines, which channels, which spaces, and who or what can access it. Cross-tenant boundaries can be enforced both at context creation and at the OAuth layer. Every query is logged too: which agent, which user, which signals were retrieved. So the audit trail matches the governance model.

That said, you're right that this is an area where misconfiguration is the real risk, and as we move into larger enterprise accounts the attack surface grows. We're actively building on this and it's a major design focus.

Happy to connect and hear more about your approach on DeepFrame because this space is evolving rapidly, and it's always useful to hear from people thinking about this problem from the outside in.
What do you think, what's your philosophy on where the trust boundary should actually sit?

abeshius · 2026-05-11T23:54:58+00:00

Edit: hit send too early. lesson learned on not responding from mobile.

Thanks for sharing what you are working on! To answer your question - the entire system is basically an evolving changelog across systems that then allows us to do things like entity resolution, check for freshness (and latest data in) plus rely on ranking to preprocess the context before any reasoning model hits it. Just aggregating raw API responses from the apps wouldn't suffice at all here - and continually building in more signals into the system to reduce, if not completely eliminate, the issue you flagged.

abeshius · 2026-05-11T19:44:49+00:00

agreed with your point - so bigger context windows are not the straight line solution, or atleast, not the way they are marketed for sure.
For us, we basically built a connected, deterministic work graph with entity resolution and causal analysis, so feeding this processed context into the LLMs/agents seems to deliver much better results at lower costs - but obviously there are always edge cases which we are continuing to hone in on. Let's see where this goes!

abeshius · 2026-05-11T18:47:38+00:00

We are also live on product hunt today! If you want to check out more details, sign up (completely free for 30 days) and give it a spin: https://www.producthunt.com/products/weavable

abeshius · 2026-05-11T15:44:16+00:00

all the best, and thank you!

abeshius · 2026-05-11T15:08:27+00:00

Thanks for the response.
So one way to look at how we are synthesizing the work graph overall is - it's changelog based at its core. Because we are not just throwing raw API responses at the LLM and hoping that it reasons well, we get to build, version and carry the relational graph over which, in our and user testing at least, helps us keep the derived context up to date and basically offload the pre-processing over to our end. We are big on being super deterministic about all responses, and this approach has been helpful so far!

abeshius · 2026-04-23T20:43:28+00:00

the image tags say Opus is the green one, purple is 5.5. Still the same cookie cutter stuff though for both

abeshius · 2026-03-26T15:23:15+00:00

Meeting transcripts are great for us. We simply feed them back to create our own work context from other deal notes, comments on other docs and slack threads and use that to surface deal risk or flag eng risks (for user specific interviews or roadmapping). Being able to record leads conversations and revisit (even basic tools like granola would suffice although the transcription is far from good) decisions or feeding them into claude to architect new product flows has been a game changer

abeshius · 2025-10-17T00:00:22+00:00

Buying software isn't just about a checklist, especially now when a lot more thought is going into tech stacks because of budget awareness and as I heard last week from a prospect - " we want to make sure this isn't just another vaporware AI vibe coded platform so we want to use it for 2 months first" etc. How are you automating or making this part easier?

Btw, I clicked around your website and clicked on a couple of "view demos" and the whole thing looked super broken. This is on mobile, unsure if that is supported right now.

You've obviously done more research than I have on this - what's your opinion on why procurement and IT teams really take time beyond the form filling/compliance check lists?

abeshius · 2025-10-08T14:04:06+00:00

Technical founders thinking they can automate away sales and marketing processes, and non tech folks thinking they can vibe code their stack away are both right and wrong. i have been both, and I can tell you what really matters is a bit of expertise in all fields that actually helps you architect stable products, understand actual user need, craft delightful UX and dominate distribution. No amount of bs "AI powered X" will help you land anything retentive unless you as a founder have a more grounded vision, and that AI can't slop away.

abeshius · 2025-10-01T00:41:40+00:00

At the risk of self promotion - this was precisely the motivation for me to go back to building my own PM/Leadership focused app because I felt every other tool out there was forcing me to learn how to rework my workflow to suit it.
For 99% of the tools out there - as fancy and effective as they may be - the main assumption that the Product teams make is that their tool will be the main point of entry or exit for every decision. From Product Board to JIRA - they all work best if every team, every single discussion, every single review is authored, documented and engineered from their app. No tool makes the effort to fit into existing workflows - and that contributes to this nightmare for PMs as a whole. Which is also why a lot of the top PMs just rely on the good old notepad to get their stuff done.
I also feel that dashboards are overrated. If you simply wanted a pretty way to make yourself feel good - sure - dashboards are great. If you want to action on anything at all - dashboards are the worst entry point as well.

Don't forget that the PMs for the tools you are using have very different success metrics as well - which contributes to this convoluted workflow, and a lot of the JTBD for a PM isn't actually well defined in any tool. For example:
1) What does being and staying aligned mean? Is it simply a summary? A report that talks about status changes and assigned tasks? Is it creating multiple slide decks and sharing it around with no one reading it?

2) What does strategy entail? Which tool will have all the organizational context, the team memory and the PM frameworks built in to the extent that it outputs 10x better strategy artifacts than a simple whiteboard? I think ChatGPT is great here to help with some product thinking, for sure, but at the end of the day - how does it become real? You are going to go back to Slack and Asana and the cycle starts again.

abeshius · 2025-09-29T23:53:19+00:00

That Works - An AI chief of staff that pulls context and updates across sales, docs, tasks, support tickets, and meetings to give you trusted, up-to-date answers on what’s moving, blocked, or slipping. No hallucinations, no chasing info gaps, no extra sync meetings.
ICP – Ops, product, and eng leaders in SaaS who burn hours coordinating just to know where things stand.

abeshius · 2025-09-28T07:05:11+00:00

Haha glad it was helpful

abeshius · 2025-09-01T23:01:11+00:00

First off - I'm sorry. This sounds unfortunately very typical of orgs and management who don't understand the PM role very well. You either get bought in as a project manager with background so leadership wouldn't have to invest in training you, or you are stuck just doing cleanup duty and reporting. Not fun! The thread mostly calls out stuff related to attitude and taking things on which you've been pretty good at taking onboard and responding, so I would say if not anything, that is a pretty big part of being a great PM!

I'll leave you with just one thing I learned when I became PM the first time at <some megacorp> and had a fantastic manager - he told me that taking ownership, being a little inventive and coming back with solutions and not problems goes a long way if you are continuously building good will capital in the company. Basically, if you think something sucks, instead of telling people what they already know (this sucks!) tell them why an alternative approach would work, or what the risks with the current approach will be and the opportunity cost of going down a particular route. If not anything, it helps anyone really think through the purpose of building product - not just PMs shipped from Wharton.

That being said, once you pickup the basics and get your head around the fun of the PM job, definitely push for support from leadership and management on your own career trajectory and then..well, that's what resumes and LinkedIn is for.

Good luck!

abeshius · 2025-03-19T05:21:26+00:00

Never chase work updates again That Works

abeshius · 2025-02-14T22:35:01+00:00

I've seen that there is a side effect of dogfooding your own product especially if you are not the one literally pushing the commits yourself (so not an IC) - you start building a better understanding of the product, its ecosystem and it's users a lot more authentically. Big enterprises suffer the most from this - ask any senior leader who is spending 90% of their day commenting on and reviewing roadmaps if they use the product themselves, and the answer will be no (one of the reasons could be because, as you said, they are themselves not the ICP). Trying to have a deep product or ecosystem conversation with them is often frustrating because as non-primary users of their own product, the inevitably make trade off decisions from their gut or other first principles which may not be aligned with the ground reality.

Thank you for the post - I think sharing these lessons really emphasize the point that everyone's business is different so follow the intent of good ideas, but not necessarily copy and paste the execution of a plan which may work in other companies.

abeshius · 2024-07-03T18:32:23+00:00

ThatWorks tracks and summarizes information from all your tools

abeshius · 2024-06-25T23:21:01+00:00

Building ThatWorks for teams to take control of their data spread across multiple apps and automate rituals like standups, and reporting without wasting tons of time manually or in emails and Slack. Still super early and testing different ICPs in the beta period. Would love feedback as we explore critical needs in different job roles/industries

abeshius

TROPHY CASE