About
Small on purpose. Senior by default.
CraneDev exists because of the systems we kept inheriting: built quickly by a team that had since moved on, documented by the commit log, and kept alive by the one person who still remembered why. We wanted to be the team that stays.
So the shape is deliberate. No account managers between you and the engineers, no bench of juniors learning on your budget, and no handover at the end to people who have never seen the code. The people who scope the work build it, and the people who build it run it.
How we work
Four rules that decide most things.
The people who scope it build it.
Estimates come from the engineers who will do the work, and they carry them through to production. Nobody sells a plan they will not have to keep.
Working software over decks.
The first thing you see is a release, not a roadmap. If a question can be answered by shipping a slice, that is how we answer it.
We say no early.
If the work is not a fit, or the plan will not survive contact with your data, we say so in the first call and point you somewhere better.
We stay on it.
Maintenance is part of the offer, not an afterthought. The system keeps its authors, and the authors keep their pagers.
What we decline
Work we turn down, so the rest gets our full attention.
- Fixed-price rewrites of systems we have not read yet.
- Staff augmentation — engineers dropped into a team we do not run.
- Projects where nobody on your side can say what done looks like.
- Work that depends on a technology choice we would not make ourselves.
Talk to the people who would do the work.
Bring the system you already have. We will tell you where we would start, what we would leave alone, and how long the first release takes.
Book a call