You build the request
A checklist of documents, a few questions, a signature if the work needs one. Build it once as a template and reuse it for every client after that.
Self-hosted · PHP Edition 1.0
Intake gives every client a private, branded page listing exactly what you need. They drop files in, answer your questions, sign, and you are done. No accounts. No attachments. No follow-up emails.
Self-hosted · Your domain · Your branding · No accounts for clients
Document request
Documents for your 2026 return
Northbank Studio needs a few documents and details from you. Everything happens on this page — there is nothing to install and no account to make.
What we need 2 of 4 received
Due Sunday 23 August · northbank.example.com
01 — How it works
No training, no onboarding call, no account to create. If they can open an email they can finish this.
A checklist of documents, a few questions, a signature if the work needs one. Build it once as a template and reuse it for every client after that.
One email, carrying a numbered list of exactly what you need. No attachments, no reply thread, nothing to install.
A page with your logo on your domain. Drag and drop, works on a phone, tells them what is still missing before they can submit.
Complete, checked against the list, and filed under the client. The chasing happens on its own until they are done.
02 — What you get
Not a feature list written to fill a comparison table — the things that decide whether a request comes back complete.
Per-folder minimums, so “three months of bank statements” is enforced rather than hoped for. They cannot submit until the list is satisfied.
Build your onboarding questions once. Applying a template copies it onto the request, so editing it later never rewrites something you already sent.
Every signature produces a PDF naming who signed, when, from which IP, and a SHA-256 digest of the whole submission. Change a byte and the digest no longer matches.
Before the deadline and after it, on your schedule. Your staff get a daily digest of what is late so nobody has to remember to look.
Local disk or any S3-compatible bucket. Files are never publicly addressable; every download is a signed, short-lived link that re-checks authorization when it is used.
Each workspace gets its own domain, logo, color, staff and clients, completely isolated. Run it for yourself or resell it.
03 — Who it is for
“We were spending the first fortnight of every engagement asking for the same six documents. Now we send one link and get on with the work.”
05 — Questions
No. They get a link that is the credential. You can give a client a portal login if they come back often, but nobody has to create one to send you a file.
Wherever you point them: the server’s own disk, or any S3-compatible provider — Amazon S3, Cloudflare R2, DigitalOcean Spaces, Backblaze. Nothing is ever served by public URL.
It captures intent, identity as far as an email address and a typed name establish it, the time, the IP address, and a tamper-evident digest of what was signed. That is the same evidentiary shape most e-signature products produce. It is not a qualified electronic signature, and we say so on the Security page rather than implying otherwise.
PHP 8.2 or newer and a database. It installs through a browser in about ten minutes — a requirements check, your database, your details, and it locks itself behind you.
There is nothing to remove. Your clients only ever see your name, your logo and your color. The word “Intake” never appears on their side.
Nothing. The software keeps working. Support expiry ends updates and help, not your right to run what you bought.
Get started
The next client who owes you documents gets a link instead of an email thread. Everything after that happens on its own.