i'm not technical. is that a problem?
not at all, and most of our clients aren't. we explain things in terms of what you control and what you'll see, without the jargon. you describe the goal; we handle the rest and tell you where things stand in words you already use.
you're the normal case. the people who hire us run clinics, logistics companies, trades, and professional services firms. they know their business cold and have no interest in learning what a reverse proxy is, which is the right attitude. our job is to translate, and to make sure you never have to trust us blindly because you couldn't check.
how we keep it understandable
- the scope says what you'll be able to do when it's done, not which framework it uses
- you get a preview link on day one. clicking through something beats reading a status report about it
- updates are short, written, and in your words: "invoices now go out automatically" rather than "cron job deployed"
- the pentest report opens with a one-page summary written for people who don't work in security
- the handover doc explains how to update content, who to call, and what runs where, written for a human, not an engineer
what we need from you
the goal, roughly when, and any constraint that matters: a budget ceiling, a deadline, a system that has to stay. you don't need to specify the solution. if we ask a technical question, it's because the answer changes the price or the date, and we'll explain why. when "not sure yet, help me figure it out" is the honest answer, that's an option on the contact form, and it's a fine place to start.
we also write things down so you're not dependent on us. if you ever want a second opinion, another engineer can read what we left and follow it. see what to include in the first message, or if you just want an hour of straight answers, that's cheap.