The Orchestrivo Handbook

What do we want to achieve

Let anyone have the impact of an engineer

We want to enable every non technical person in a company to solve their own problems without needing to loop in a technical team. Anyone should be able to deploy their own AI powered tools that 10x their teams productivity without needing to write a large spec, sync with leadership, allocate budget etc.

Understanding the task should be the only requirement for automating it, no other expertise required.

Get our users promoted

Almost every existing business has massive inefficiencies. We notice Orchestrivo starts to spread internally within a company when a "champion" starts automating work and showing their coworkers.

This champion always has the same 3 characteristics:

1. They understand the problem(s)
2. They know what AI can do
3. They know Orchestrivo exists

If you're reading this post you probably have #3 locked down (or you're super lost). 1 and 2 tend to come naturally to that person because they spend time around the problem as a result of their job and they're excited by AI enough to frequently use LLMs.

This person will often become the "AI person" internally and will make their leadership team shed a tear of joy because they're finally "leveraging AI" like the CEO asked, but in a useful way.

We want to be their secret weapon that makes their division 10x more efficient and gets them or their team promoted.

Edit: 3 of these users went as far as joining Orchestrivo full time. They were power users from , and but now work at Orchestrivo because they wanted to help more of the world feel the magic.

Where We're Going

We want Orchestrivo to be such an outstanding product that marketing is an afterthought. Word of mouth from thrilled users should be our main growth engine. To get there, we have some core improvements to make to the platform that we're building towards.

Become the operating system for enterprise automation

We started off focusing purely on workflow automation but things have evolved into something much more powerful.

With every layer we've added, we've seen Orchestrivo turn into more and more of a central piece of AI infrastructure that businesses rely on. It's becoming a single offering that has everything an enterprise needs to become AI native. We've been working to address every question enterprises have when rolling out agents. How do you build agents, share them, manage data access, see what they did, manage spend? Every question here and more is addressed with Orchestrivo.

We've realized how powerful this is and will keep building in this direction until Orchestrivo is a must have for every enterprise.

Make automating fun

We want people to be excited to build on Orchestrivo. It should be something they look forward to.

Every decision we make should be in pursuit of that. Obviously the core functionality should be snappy, scalable and handle every workload but the finer details and UX are equally as important. Everything from loading animations, to keyboard shortcuts, to notification emails matter.

We're going to keep improving the user experience until we're in the same category products like Linear, Figma, Apple etc.

How We Make Users Happy

One key differentiator between us and competitors is how much effort we put into caring for our users.

Support

Orchestrivo can be used in an infinite number of ways. That's great but it also means our users can get stuck, confused or frustrated in an infinite number of ways.

Having absolutely top tier support plays a key part in ensuring our early users have a great experience. We take great pride in it as well.

Same day shipping

We used to joke that we were like Amazon because we had "same day shipping". When a customer would request a new integration or feature we'd try to get it out by that night's release.

Obviously this velocity got a bit harder to maintain as our user base grew but we still try to build customer feature requests as quickly as we possibly can.

Users seeing features they request in the product within days helps prove we're truly building for them. They can participate in steering product direction by just asking.

Listening to feedback and iterating constantly

Every time a user complains about anything at all, we write it down and try to act on it somehow. The first version of our automation builder was an unusable hunk of garbage. Orchestrivo has only become what it is today because of thousands of small iterations that were driven by direct user feedback.

Sometimes this is super straight forward when people message us saying "here's some feedback". Most of the time it comes in unexpected ways. Every support ticket, unexpected error or confused clicks during a demo call is feedback in its own right.

We try to keep our iteration cycles extremely short so tweaks to the product can be felt continuously. Most of the time we're shipping updates nightly to address the days feedback!

Strive to feel embarrassed

Looking back at demo videos from even a month ago should feel embarrassing. If we're not embarrassed, the product isn't improving fast enough and we're failing our users.