About Stagely
Built at the kitchen table of a landscape studio.
I'm married to a landscape architect. For years I watched a small, serious studio run itself on spreadsheets, a shared drive and a very good memory. Fee proposals rebuilt from the last one. Issue sheets kept by hand. The question "have we invoiced Stage 3 yet" answered by scrolling.
None of the tools on the market fit. They were built for agencies, or for construction, or for everyone, which is the same as nobody. Nothing knew what a RIBA stage was, or that a sub-stage can be out of scope, or that an invoice needs a VAT number before it goes anywhere.
So I built one that did.
Who I am
Decades of software where getting it wrong is expensive.
I've spent more than twenty years building software for organisations that cannot afford it to be wrong: broadcasters, publishers, some of the biggest names in retail, and the fast-growing companies trying to catch them. That work teaches the unglamorous things that matter.
Money is never a floating point number. Every document you send keeps a copy of the rates it was priced on. A backup is only real once you have restored from it.
Stagely gets all of that, because I didn't know how to build it any other way.
How it's run
Small, and I'd rather you knew that than found out.
There is no sales team and no support queue. If something is wrong, the email lands with the person who wrote the code, and it gets fixed, usually the same day.
Your data is backed up every hour, and I practise restoring it. Every fee proposal and invoice you send is frozen as sent, so last year's rates stay on last year's documents.
It started in a landscape studio. Architecture practices run on the same Plan of Work, which is why it fits them too, and why the second practice to join is one.
What it isn't
It isn't trying to be everything. It won't replace your accounts package or your drawing software. It does the running of the practice, and it does that part properly.
If you want to talk it through, email me. It really will be me.
Roy Shay