This content originally appeared on DEV Community and was authored by Avery Brooks
Hey dev.to community!
I’m excited to share a project I’ve been working on—ClearWork, a platform built to capture how work really happens, design better processes, and enable AI-augmented execution in modern teams. We’re looking for your honest feedback, questions, and ideas!
What is ClearWork?
ClearWork is an end-to-end transformation platform that:
Maps real user activity (not just interviews or self-reports)
Designs the future state with AI-assisted requirements and process diagrams
Drives adoption in-app and orchestrates AI agents for real workflow improvements
No keylogging, no field contents, no screenshots—just actionable events and metadata with a privacy-first approach.
Key Features
Live Process Maps: Instantly visualize actual workflows and compare variants. Find bottlenecks, delays, and compliance drift.
AI-Supported Future-State Design: Automatically draft user stories, swim lanes, and requirements directly from observed work.
Adoption & Agentic Orchestration: Contextual in-browser guidance for users; coordinate the actions of AI agents with auditability and ROI tracking.
Continuous Improvement: Iterate based on real usage metrics and feedback.
Why we built this
Most process tools stop at diagrams or analytics, and change efforts struggle when “the way things actually work” is unknown. ClearWork grounds transformation and automation in reality, not assumptions—enabling teams to shape better systems and make changes that stick.
What Makes Us Different
No “lift-and-shift”: We work to fix broken processes, not just automate the past.
Privacy-centric data capture: Only events + metadata, full control over what’s collected.
Measurable outcomes: Track real improvements in cycle time, adoption, and business value.
How Can dev.to Help?
What stands out from this approach (good or bad)?
What blockers do you foresee for teams considering something like this?
If you’ve built, implemented, or evaluated process mapping/automation tools, what’s missing (feature or philosophy)?
Anything unclear or that you’d like to see clarified in the product or story?
We’d love to hear your reactions, concerns, or war stories—raw or refined!
If you’re interested in a test drive or want to follow along, check out clearwork.io/products and let us know what you think.
Thanks so much!
— The ClearWork Team
This content originally appeared on DEV Community and was authored by Avery Brooks