sheet 02 — your path
Something's broken and nobody will touch it
Easy. First we read what you have. Then we tell you the truth. Only then do we touch anything.
The previous company disappeared. We don't.
Code with no documentation, invoices for "maintenance", a phone nobody answers. We've seen the pattern enough times to stay calm about it. You don't need to know what exactly you have — finding that out is part of the job.
Ask:
That's why we read first. The audit is read-only, and every fix afterwards has a way back.
I'm scared you'll touch one thing and the rest falls over.
That's why we read first. The audit is read-only, and every fix afterwards has a way back.
I don't even know what I have or where.
Normal. We list what exists, who holds access, and what belongs to whom. You get it in writing.
Audit. Plan. Then a repair — or an honest "leave it".
The audit changes nothing in your system; it only reads. You get a plain-language write-up: what works, what's about to fail, what we'd fix and for how much, and what isn't worth fixing. Every later change is reversible. That's a condition, not a promise. Some closed systems we don't service — we'll say so on the first call and point you to someone who does.
A fixed price for the audit, known before you say yes.
The audit costs a fixed amount depending on the size of what you have. No "it depends" stretched across three meetings. After the repair, most clients stay on a small monthly care plan: hosting, updates, small fixes, a phone that gets picked up. Boring. Boring is good.
Talk?
What you picked is already in the message. No need to repeat yourself or write anything formal.