Skip to content
Intake Document collection

Self-hosted · PHP Edition 1.0

Stop chasing clients for paperwork

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

Northbank Studio REF 000412

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

  • 01 Signed engagement letter 1 of 1
  • 02 Bank statements 1 of 3
  • 03 Receipts and invoices optional
  • 04 Photo ID 1 of 1
Send your documents →

Due Sunday 23 August · northbank.example.com

00 Accounts a client must create before sending you a file
04 Statuses from sent to complete, and no more
12 Question types, from a date to a signature
∞ Workspaces on one installation

01 — How it works

Four steps, and the client does two of them

No training, no onboarding call, no account to create. If they can open an email they can finish this.

01

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.

02

They get a link

One email, carrying a numbered list of exactly what you need. No attachments, no reply thread, nothing to install.

03

They drop files in

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.

04

You get everything at once

Complete, checked against the list, and filed under the client. The chasing happens on its own until they are done.

02 — What you get

Everything the job actually needs

Not a feature list written to fill a comparison table — the things that decide whether a request comes back complete.

Document checklists

Per-folder minimums, so “three months of bank statements” is enforced rather than hoped for. They cannot submit until the list is satisfied.

Reusable templates

Build your onboarding questions once. Applying a template copies it onto the request, so editing it later never rewrites something you already sent.

Signatures with an audit record

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.

Reminders that run themselves

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.

Storage that is actually private

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.

Many firms, one installation

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

Anyone who cannot start until the client sends something

  • 01 Accountants and bookkeepers Year-end packs, receipts, statements
  • 02 Law firms Identity documents, signed engagement letters
  • 03 Mortgage and finance brokers Payslips, IDs, proof of address
  • 04 Design and marketing agencies Brand assets, copy, approvals
  • 05 Recruiters Right-to-work checks, references
  • 06 Immigration advisers Passports, certificates, evidence bundles
“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.”
A firm that replaced its email thread

05 — Questions

Answered plainly

01 Do my clients need an account?

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.

02 Where do the files actually live?

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.

03 Is the signature legally binding?

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.

04 What do I need to run it?

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.

05 Can I remove your branding?

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.

06 What happens when support runs out?

Nothing. The software keeps working. Support expiry ends updates and help, not your right to run what you bought.

Get started

Install it, point a domain at it, and stop chasing.

The next client who owes you documents gets a link instead of an email thread. Everything after that happens on its own.