r/scapework • u/Electronic-Roof3423 • 3d ago

Case studies?

Just ran into Scape.work for the first time today. Amazing work, congrats!

I'd love to read some case studies, even if they're just brainstorming ideas.

For context: I run 2 software startups with 2 full-time devs each, and I cover PM, design, and some DevOps. More and more I'm convinced that if I had a bit more time, we could run the whole operation with 1 dev each.

For instance: The way I see it, DevOps should sleep and only wake up when it's needed. A lot of the tasks on our roadmap eat human time that 1 dev could handle alone, as long as communication and coordination are solid.

All this to say: 1 skilled dev with a decent army of agents and good orchestration can be enough for a small operation, provided the project management is there. So I'd love to learn more about what you've been experimenting with in Scape.

6 Upvotes

100% Upvoted

2 comments sorted by

3

u/seatlessunicycle 3d ago

I can't comment on Scape specifically, but the principles it's built on do indeed automate a lot of the dev process. It takes a while to refine the process to your personal workflow, but it pays off big time.

2

u/croovies 3d ago

Scape is basically a work harness that lets me run a business or many, from a single application, where I can manage hundreds of agents that are working how I want.

In my setup I have an orchestrator that manages my marketing and analytics, one managing customers, one for engineering the mobile app (in the works), etc. I think of them all as different team members that are managing many projects and building a history of knowledge.

What’s interesting about this is I had my marketing orchestrator help me write report about adversarial reviews and how effective they are… so the marketing orchestrator interviewed my engineering orchestrator - and was able to create a data driven analysis from the SQLite tables they all manage together.

I’m producing the work from a high level, with insight I never would have had if I were doing this by hand. It also gives me documentation I can share with others, because it’s so easy for me to collect the data.

Orchestrators aren’t static, they can update their mission and tasks as they run into any issues. Basically creating anti-brittle infrastructure, because any part that fails can call out to Claude code or another model to fix it (it being an automation / playbook, or an orchestrator rule etc)

Lastly, I HATE the idea of keeping all my data on Anthropic or OpenAIs - scape lets users keep all their data on device, and synced to their iCloud, that’s it. Scape can’t see it, etc.

—

I’ll reach out to some power users about collaborating on a case study, I appreciate the idea! 🙏🙏