u/Sad_Lab8670

Building something around AI + operations, and looking for a few design partners.

I’ve been exploring a problem that feels increasingly common in growing teams:

• workflows breaking across handoffs,
• constant followups,
• operational chaos living in Slack,
• people acting as glue between tools/processes,
• founders/operators needing to constantly “watch” things so they don’t slip.

Things work but only because someone is constantly following up, checking in, reminding people, updating statuses, pushing things forward, etc. not necessarily what they should be spending their time on.

Hearing things like "My senior ops manager spent 6 hours yesterday chasing invoice approvals. That's not what I'm paying her for." is so common.

Most automation tools seem focused on automating steps. I’m more interested in whether AI can continuously own and drive workflows forward while still keeping humans involved for approvals, judgment, and edge cases.

The core idea is persistent AI sessions that maintain operational continuity over time instead of acting like one-off chatbots/copilots.

I’m still early and intentionally looking to co-design this with a handful of startups/agencies/ops-heavy teams facing real execution bottlenecks.

Not selling anything right now. Mostly trying to:

• deeply understand operational pain,
• identify workflows that are painful to babysit,
• learn where trust breaks with AI systems,
• and build something genuinely useful alongside real teams.

If your team struggles with operational coordination, repetitive followups, workflows slipping through cracks, or execution overhead, I’d love to chat.

Even if it’s just exchanging notes on where things start becoming messy as teams scale.

Building something around AI + operations, and looking for a few design partners.

I’ve been exploring a problem that feels increasingly common in growing teams:

• workflows breaking across handoffs,
• constant followups,
• operational chaos living in Slack,
• people acting as glue between tools/processes,
• founders/operators needing to constantly “watch” things so they don’t slip.

Things work but only because someone is constantly following up, checking in, reminding people, updating statuses, pushing things forward, etc. not necessarily what they should be spending their time on.

Hearing things like "My senior ops manager spent 6 hours yesterday chasing invoice approvals. That's not what I'm paying her for." is so common.

Most automation tools seem focused on automating steps. I’m more interested in whether AI can continuously own and drive workflows forward while still keeping humans involved for approvals, judgment, and edge cases.

The core idea is persistent AI sessions that maintain operational continuity over time instead of acting like one-off chatbots/copilots.

I’m still early and intentionally looking to co-design this with a handful of startups/agencies/ops-heavy teams facing real execution bottlenecks.

Not selling anything right now. Mostly trying to:

• deeply understand operational pain,
• identify workflows that are painful to babysit,
• learn where trust breaks with AI systems,
• and build something genuinely useful alongside real teams.

If your team struggles with operational coordination, repetitive followups, workflows slipping through cracks, or execution overhead, I’d love to chat.

Even if it’s just exchanging notes on where things start becoming messy as teams scale.

Building something around AI + operations, and looking for a few design partners.

I’ve been exploring a problem that feels increasingly common in growing teams:

• workflows breaking across handoffs,
• constant followups,
• operational chaos living in Slack,
• people acting as glue between tools/processes,
• founders/operators needing to constantly “watch” things so they don’t slip.

Things work but only because someone is constantly following up, checking in, reminding people, updating statuses, pushing things forward, etc. not necessarily what they should be spending their time on.

Hearing things like "My senior ops manager spent 6 hours yesterday chasing invoice approvals. That's not what I'm paying her for." is so common.

Most automation tools seem focused on automating steps. I’m more interested in whether AI can continuously own and drive workflows forward while still keeping humans involved for approvals, judgment, and edge cases.

The core idea is persistent AI sessions that maintain operational continuity over time instead of acting like one-off chatbots/copilots.

I’m still early and intentionally looking to co-design this with a handful of startups/agencies/ops-heavy teams facing real execution bottlenecks.

Not selling anything right now. Mostly trying to:

• deeply understand operational pain,
• identify workflows that are painful to babysit,
• learn where trust breaks with AI systems,
• and build something genuinely useful alongside real teams.

If your team struggles with operational coordination, repetitive followups, workflows slipping through cracks, or execution overhead, I’d love to chat.

Even if it’s just exchanging notes on where things start becoming messy as teams scale.

Building something around AI + operations, and looking for a few design partners.

I’ve been exploring a problem that feels increasingly common in growing teams:

• workflows breaking across handoffs,
• constant followups,
• operational chaos living in Slack,
• people acting as glue between tools/processes,
• founders/operators needing to constantly “watch” things so they don’t slip.

Things work but only because someone is constantly following up, checking in, reminding people, updating statuses, pushing things forward, etc. not necessarily what they should be spending their time on.

Hearing things like "My senior ops manager spent 6 hours yesterday chasing invoice approvals. That's not what I'm paying her for." is so common.

Most automation tools seem focused on automating steps. I’m more interested in whether AI can continuously own and drive workflows forward while still keeping humans involved for approvals, judgment, and edge cases.

The core idea is persistent AI sessions that maintain operational continuity over time instead of acting like one-off chatbots/copilots.

I’m still early and intentionally looking to co-design this with a handful of startups/agencies/ops-heavy teams facing real execution bottlenecks.

Not selling anything right now. Mostly trying to:

• deeply understand operational pain,
• identify workflows that are painful to babysit,
• learn where trust breaks with AI systems,
• and build something genuinely useful alongside real teams.

If your team struggles with operational coordination, repetitive followups, workflows slipping through cracks, or execution overhead, I’d love to chat.

Even if it’s just exchanging notes on where things start becoming messy as teams scale.

Building something around AI + operations, and looking for a few design partners.

I’ve been exploring a problem that feels increasingly common in growing teams:

• workflows breaking across handoffs,
• constant followups,
• operational chaos living in Slack,
• people acting as glue between tools/processes,
• founders/operators needing to constantly “watch” things so they don’t slip.

Things work but only because someone is constantly following up, checking in, reminding people, updating statuses, pushing things forward, etc. not necessarily what they should be spending their time on.

Hearing things like "My senior ops manager spent 6 hours yesterday chasing invoice approvals. That's not what I'm paying her for." is so common.

Most automation tools seem focused on automating steps. I’m more interested in whether AI can continuously own and drive workflows forward while still keeping humans involved for approvals, judgment, and edge cases.

The core idea is persistent AI sessions that maintain operational continuity over time instead of acting like one-off chatbots/copilots.

I’m still early and intentionally looking to co-design this with a handful of startups/agencies/ops-heavy teams facing real execution bottlenecks.

Not selling anything right now. Mostly trying to:

• deeply understand operational pain,
• identify workflows that are painful to babysit,
• learn where trust breaks with AI systems,
• and build something genuinely useful alongside real teams.

If your team struggles with operational coordination, repetitive followups, workflows slipping through cracks, or execution overhead, I’d love to chat.

Even if it’s just exchanging notes on where things start becoming messy as teams scale.

Building something around AI + operations, and looking for a few design partners.

I’ve been exploring a problem that feels increasingly common in growing teams:

• workflows breaking across handoffs,
• constant followups,
• operational chaos living in Slack,
• people acting as glue between tools/processes,
• founders/operators needing to constantly “watch” things so they don’t slip.

Things work but only because someone is constantly following up, checking in, reminding people, updating statuses, pushing things forward, etc. not necessarily what they should be spending their time on.

Hearing things like "My senior ops manager spent 6 hours yesterday chasing invoice approvals. That's not what I'm paying her for." is so common.

Most automation tools seem focused on automating steps. I’m more interested in whether AI can continuously own and drive workflows forward while still keeping humans involved for approvals, judgment, and edge cases.

The core idea is persistent AI sessions that maintain operational continuity over time instead of acting like one-off chatbots/copilots.

I’m still early and intentionally looking to co-design this with a handful of startups/agencies/ops-heavy teams facing real execution bottlenecks.

Not selling anything right now. Mostly trying to:

• deeply understand operational pain,
• identify workflows that are painful to babysit,
• learn where trust breaks with AI systems,
• and build something genuinely useful alongside real teams.

If your team struggles with operational coordination, repetitive followups, workflows slipping through cracks, or execution overhead, I’d love to chat.

Even if it’s just exchanging notes on where things start becoming messy as teams scale.