contact
tell us what's blocking you
a build, a bug, a breach, a spreadsheet that's become load-bearing. one message is enough to start, and we'll ask the rest.
~/rebootworks/contact
what happens next
0001
a human reads it.within one business day, mon–fri. the reply is typed by one of us.
0002
we ask two or three questions.by email, so you can answer when it suits. a call only if it's faster.
0003
you get a written plan.scope, approach, timeline, and one fixed number. yours to keep either way.
direct
email hello@rebootworks.dev
replies within one business day, mon–fri.
mid-incident?
if you're being attacked, defaced, or locked out right now, email us with "incident" in the subject line and we'll prioritise it.
not sure what you need?
say that. "something's wrong and I don't know what" is a perfectly good first message, and working out what's wrong is part of the job.
man contact
before you write
Q:what should I include in the first message?▸
what you're trying to achieve, roughly when, and any constraint that matters: a budget ceiling, a deadline, an existing system you have to keep. links to what you already have help more than a long description.
Q:do you charge for the initial call?▸
no. scoping conversations and the written plan that follows are free. we only invoice once you've agreed a scope and a number in writing.
Q:we're tiny. is there a minimum?▸
small projects are welcome, and a landing page or a one-day fix is real work. if something is too small to be worth engaging us for, we'll say so and tell you how to do it yourself.
Q:can you sign an nda before we talk?▸
yes. send yours over and we'll sign it before the first call. we're happy to work under your paperwork rather than insisting on ours.