Looking for a collaborator to explore async workflow design
I have been studying how real time agent workflows behave inside sales systems, especially after seeing Sellinger AI in action this week.
Now I am looking for someone who wants to explore this area together.
The goal is simple:
• Experiment with async timing rules
• Compare workflow structures
• Share insights from real use cases
• Build small prototypes or system sketches together
You do not need deep technical experience.
Curiosity and consistency matter more for this kind of work.
If you are interested, let me know and I can share more about the rhythm based framework I have been building.
Quiet structure, steady flow.
Trending on Indie Hackers
Hi Koni, this sounds really interesting! I’ve been exploring async workflows in different tools, and I’d love to contribute some ideas or help visualize the processes. I also create visual mockups and illustrations that make complex workflows easier to understand.
If you’d like, I can draft a small example or sketch of one of your async flow ideas to see how it could look in practice. Happy to collaborate and share insights
Thanks for offering to sketch out a flow. I might reach out when I structure the first timing model. Good to connect here.
Thanks for your response and i will like you to share your gmail or contact where we can reach out to each other and discuss frequently on this
Sure, happy to connect.
Here’s my Gmail: [email protected]
We can explore a small async flow sketch together and see where it leads.
Hello Koni, this is great if you're looking for a UI/UX Designer to help you build idea around this for prototyping test, you can share your contact details. Let's discuss more.
Thank you
Thanks for your message!
A UI/UX perspective could definitely help shape some of the prototype tests I’ve been running.
If you’re open to it, we can start with a simple async exchange.
You can reach me at [email protected], and I’ll share a short outline of what I’ve been experimenting with on the workflow side.
Looking forward to hearing your thoughts.
Really interesting angle, Koni. A lot of founders are trying to understand how agent workflows behave, but very few talk about the timing, structure, and real-world patterns behind them
I work with SaaS and AI builders on Reddit, helping them validate early ideas, attract the right users, and communicate their value clearly without sounding technical or confusing. What you’re exploring here is exactly the kind of topic that sparks deep engagement when positioned the right way
If you’re open, I’d love to share a few Reddit growth frameworks that could help you attract more collaborators, testers, and real use-case discussions around your rhythm based approach
DM me anytime happy to exchange ideas
I would appreciate some advice on SaaS as well - I've built a student membership app using Java and React but now need to figure out how to ship the app to an interested client. Any advice would be great!
Thanks for sharing this and congrats on getting your student membership app to this stage. That’s already a solid milestone
When it comes to shipping it to an interested client, the process really depends on how you want to package it: hosted SaaS, self-hosted install, or a hybrid setup. I’ve helped a lot of early-stage SaaS builders on Reddit position and deliver their products in a way that feels client-ready without overcomplicating the tech side
If you want, I can break down a simple delivery framework for you setup, onboarding flow, pricing structure, and how to present it so the client sees immediate value
DM me anytime and I’ll walk you through the next step
Thanks for the thoughtful breakdown. I really appreciate how clearly you framed the timing and structure side of early-stage workflows.
Reddit growth frameworks sound valuable, especially for testing how different timing rules behave across communities. I’d be happy to exchange ideas and learn from your experience.
Since IH doesn’t support DM, you can reach me at [email protected] and we can continue the discussion there.
Quiet structure. Steady flow.
Have inbox you
check your DMs
This is a really intriguing area — most people talk about which tools teams use for async work, but the real challenge often lies in how timing and structure affect decision momentum and clarity, especially when silence gets mistaken for alignment.
One pattern I’ve noticed is that micro-decision checkpoints (small state changes that happen before a big decision) help make progress visible without forcing heavy overhead. When participants can implicitly signal readiness or hesitation, async systems feel directional instead of stalled.
Curious — in your experiments so far, are you finding timing rules that work best for prompting action versus those that help surface blockers early?
Hi Koni,
I'm a software engineer and indie developer based in Chennai, focusing on AI-enhanced workflow automation and BPMN 2.0 process orchestration for sales/enterprise environments. I've built prototypes integrating asynchronous timing rules using tools like Camunda, Spring Boot, and React.js—recently explored agent-driven workflows and mobile apps targeting "doomscrolling" behavior.
Your rhythm-based framework resonates with my experience, particularly around experimenting with timing rules and workflow structures in real use cases.
I'd love to contribute, share architectural insights, and help validate ideas with working system sketches or prototype code. Collaboration around async agent flows and practical system design is exactly the kind of project I'm interested in.
Let's connect and explore how our approaches can complement each other—feel free to DM or share more details!
Good