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.
The backend can get complicated. Our workflows are stored as a directed acyclic graph, and each action is scheduled. There are also dynamic data placeholders, error handling, and much more. I’ve seen users create custom webhooks called “send text message” that hit their API.
Are you using React? I recommend checking out react flow if you want a UI-only solution.
home page could use some improvements. Again, all feedback is welcome and appreciated.
A real world example: You are a dev at a real estate software company. You want to allow your users to send an email, send a text, and perform a webhook when a lead signs up. We have created developer tools (API, SDK, UI components) so you can accomplish this in your app with ease.
I seem to be your target market as well (CTO of a real estate software company), but the homepage is not very clear. Perhaps the GIF next to your "triggers" section should be at the top. Also, I'd like to see a demo of the workflows being triggered. Currently I can only see the workflow editor in action.
Noted. I also like the idea of workflow's actions performing. Currently, it executes as it would in production but communication is disabled for the demo (emails won't send, webhooks won't POST). Thanks for the feedback!
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