Embed Workflow (https://embedworkflow.com). Embeddable workflow builder for SaaS platforms. Your users design and run their own workflows inside your product.
5+ years now, bootstrapped. I still write most of the code. The product itself isn't AI, it's orchestration. Visual builder, triggers, delays, webhooks, execution logic. Some of our users do wire up AI models or agents through it, but the core is just helping non-technical people build automations for our clients product.
I'm building Embed Workflow (https://embedworkflow.com), an embeddable workflow builder for SaaS platforms. Your users design and run their own workflows inside your product.
Been at it for 5+ years, bootstrapped, small team. I'm a programmer first and still get to ship code daily. Also do demo calls every week. That's where I learn the most. Own product too and say no to features a lot. No investors either, which means nobody's breathing down our neck about growth.
Finishing up a workflow testing interface today. First time we've had one. I heard "this is industry standard! You need it" on demo calls forever, but nobody ever really pushed. Workarounds were good enough for our clients, and their users don't really care, they're mostly non-technical anyway. Regardless, the other night after putting the kids down I felt like knocking it out. I'll admit though, now that I have it... I wonder how I didn't do this earlier.
We're building an in-app workflow builder that SaaS companies embed directly into their platforms—letting their users automate processes without leaving the app.
Looking for a Support Engineer (10-15 hrs/week) to help developers integrate our product, troubleshoot issues, and shape our documentation. Technical background required—you should be comfortable reading code and understanding APIs.
Competitive hourly rate, flexible hours, real product influence. 1-2 month trial with path to grow as we do.
people want easier and if you hold a shiny object in front, most will lunge for it. Developers have been benefiting greatly for some time now. High paying jobs, no ceiling in business, praise from colleagues, respect from family, etc. Non-devs close to it now have this opportunity.
No one knows what the impact of AI code gen will be on developers. But if AI code gen under delivers and the demand on truly talented devs rise, then the ones 'doing the hard work' now and maintaining their craft by human coding will win big.
You're an early adopter, so you're seeing massive gains. But eventually everyone gets the same productivity boost and that becomes the new baseline expectation.
Any clever prompting techniques that give you an edge today will evaporate quickly. People figure out the tricks, models absorb them, and tools automate them away.
There's no substitute for actually coding to learn software development. For new engineers, I'd strongly recommend limiting AI code generation on real work. Use it to explain concepts, not do the work for you. Otherwise you'll never develop the judgment to know what that 10% actually is.
Malleable and opinionated aren't mutually exclusive. The best products that solve non-core business processes should be opinionated, that's their value prop.
But yeah, the demand for webhooks, integration options, embedding's will win IMO. I imagine more demand for API-first products.
good question. I think the community fell off and many plugins were left unmaintained. I was using it for over a decade up until recently. ST4 had so many plugin issues and it stopped being worth manually fixing.
we lost something important with AI code gen... those technical barriers that used to filter for actual engineering competence. Now everyone and their mother is launching SaaS products.
I've been thinking about how AI code gen affects different teams. I think it makes good teams better and bad teams worse.
Got me thinking about how it applies to the build/buy formula. Curious what others think about this:
- Good teams with resources will be super picky about vendors and just build if they don't trust you
- Good teams without resources will lean toward building
- Bad teams will build everything initially, accumulate insane tech debt and then heavily favor buying
I've always blamed the "rails can't scale" take on how easy it is for inexperienced devs to build full stack apps. But code gen has 1000x this so I'd imagine that will fade.
It was a hard requirement for us to make our dev tool 100% embeddable without iframes. From the vendor's perspective, it's an opportunity to differentiate from competitors and avoid potential future iframe limitations that others have mentioned.
This was my instinct when we first started, and years later, on 50% of sales calls someone asks if we use iframes (as a concern). Our enterprise clients don't want to highlight a third-party solution, and iframes scream "not native" to their users.
The technical challenges of avoiding iframes are real, but the business case for solving them has been clear for us.
Embed Workflow is an API-first company bringing a native workflow builder to our customer's end-users. We are a lean self-funded team looking for strong ICs to round out our early engineering team.
Embed Workflow is an API-first company bringing a native workflow builder to our customer's end-users. We are a lean self-funded team looking for our first key hires.
5+ years now, bootstrapped. I still write most of the code. The product itself isn't AI, it's orchestration. Visual builder, triggers, delays, webhooks, execution logic. Some of our users do wire up AI models or agents through it, but the core is just helping non-technical people build automations for our clients product.