Funnalized
DEENTell me when it starts
Module 05 · Customer portal

Your brand, your domain — we stay in the background

Accept quotes, sign contracts, view invoices — on your own domain, in your colours.

0Capabilities
0Paths through
0Handovers
0Entries in the catalogue

Screens from a demo workspace. Companies, people and figures are fictitious.

What it does

Customer portal at work

Four capabilities people actually open Customer portal for. Everything else it can do is listed in full in section 04 — this is only what stands on its own.

The load-bearing capability

Your brand right into the sign-in screen

Over fifty design fields make the portal yours — logo, colours, typeface, header and sidebar, the entire sign-in screen and the document pages that go out by link. Your customer signs in and reads your name; once a logo is set — in the portal, in the company details or on the workspace — the portal’s pages show no “Funnalized”, and neither do the eleven email templates sent to them. With a domain of your own, little of us remains: our icon in the browser tab, for instance, and what our system service sends them — invitations from an automation or codes for the document pages, for example — carries your name but comes from an address under funnalized.app; without a domain of your own, our address also shows in the address bar and in the links in the emails.

50+ fields

design fields make the portal yours — into the sign-in, the document pages and the eleven email templates

Accept the quote — a rule creates the order

Your quote sits ready in the portal. The customer accepts and signs with a finger, the keyboard or an uploaded PDF. One rule is enough — “quote accepted → create order” — and in the second they accept, the order appears and flows back into your sales pipeline, with nothing for you to type.

One rule

is enough — the order appears the second they accept, with nothing for you to retype

Sign contracts digitally, with proof

The customer signs the contract directly in the portal, countersigned by you if you wish. Every signature records IP address, device and a checksum of the signature; with the signature, the contract value updates automatically in the customer record. No printing, no scanning, no post.

IP · device · checksum

is recorded for every signature; with it, the contract value follows into the customer file automatically

View invoices, report a payment

An open record

the report reaches you for internal confirmation — no more chasing emails

Your customer finds their invoices themselves at any time and reports a payment they have made with one click. The report arrives with you as an open item for internal confirmation — an end to “did you receive my transfer?” emails.

Handovers

What Customer portal receives and passes on

Comes in to Customer portal
Customer portal
Goes out of Customer portal

The customer portal is the outside: what the client sees, accepts and signs. What happens internally is carried by Sales & CRM and Projects.

Complete

Everything that is in it

0Entries in the catalogue

40 capabilities in 5 groups — complete, not curated.

Honestly

What it does not do

Every limit names the place where it happens instead.

  • No self sign-up.

    Access starts with an invitation you hand out. On first opening it, your client sets a password of their own — an account only ever comes into being through you, never through them.

  • The client does not work inside the project.

    They see the status. Tasks, sprints and internal notes stay inside — that is a decision, not a gap.

  • No payment in the portal.

    Invoices can be viewed and the client can report a payment. Collection runs through your route, not ours.

Follow-up

What teams want to know beforehand

Does the client see that Funnalized is behind it?

With a domain of your own, hardly: your own logo and colours right into the login, and invitations you send yourself, as well as password and ticket emails, go out from your own mailbox. We are not entirely invisible, though — the browser tab, for example, shows our icon, emails from our system service (invitations from an automation or codes for the document pages, for instance) carry your name but come from an address under funnalized.app, and without a domain of your own our address shows in the address bar and in the links in the emails.

How does a client get their access?

Through an invitation from you. The link is time-limited and can be revoked; on first opening it, the client sets their own password — to your password policy. If they forget it later, the forgotten-password route in the portal helps them, without them having to ask you.

Can the client export their own data?

Yes, as a GDPR data export in the portal. That is not a concession but the most convenient route — otherwise the request lands on your desk.

All 40 entries as a list

Your brand, not ours 10

  • Your brand right into the sign-in screen Over fifty design fields make the portal yours — logo, colours, typeface, header and sidebar, the entire sign-in screen and the document pages that go out by link. Your customer signs in and reads your name; once a logo is set — in the portal, in the company details or on the workspace — the portal’s pages show no “Funnalized”, and neither do the eleven email templates sent to them. With a domain of your own, little of us remains: our icon in the browser tab, for instance, and what our system service sends them — invitations from an automation or codes for the document pages, for example — carries your name but comes from an address under funnalized.app; without a domain of your own, our address also shows in the address bar and in the links in the emails.
  • On your own domain Run the portal on portal.your-company.com with its own SSL certificate instead of a foreign address. The URL in the address bar belongs to you.
  • Your own domain with its own SSL certificate, or a subdomain
  • Over fifty design fields — portal, sign-in screen and document pages styled separately
  • Eleven branded email templates of your own to your customers
  • Eight font pairings from our own server You choose the typeface from eight matched font pairings or take the system font. It really arrives in the portal, on the sign-in screen and on the document pages — the files sit on our own server, and opening the portal sends no request to a font service.
  • Colour sets that stay readable Eight ready-made colour sets or the colours of your workspace, plus four corner roundings and three densities. The app picks the text colour on coloured backgrounds so that it keeps a contrast of at least 4.5 : 1 — on a light brand colour the button text turns dark instead of white.
  • Five navigations, six start pages The menu as a sidebar, as a header with tabs and in three further forms; the start page as cards, list, table, key figures and in two further layouts. The preview in the settings shows the same building blocks as the real portal — what you see there is what your customer sees.
  • Logo, company name, footer text, legal links and colours come as defaults from the workspace — per field keep, adjust, return to the default or hide; without a logo of its own, the workspace logo appears
  • For the document pages that go out by link you choose one of four layouts — from the full coloured header to the letter without one

Signed, without paper 8

  • Accept the quote — a rule creates the order Your quote sits ready in the portal. The customer accepts and signs with a finger, the keyboard or an uploaded PDF. One rule is enough — “quote accepted → create order” — and in the second they accept, the order appears and flows back into your sales pipeline, with nothing for you to type.
  • Sign contracts digitally, with proof The customer signs the contract directly in the portal, countersigned by you if you wish. Every signature records IP address, device and a checksum of the signature; with the signature, the contract value updates automatically in the customer record. No printing, no scanning, no post.
  • Accept documents — with no sign-in at all Quotes and contracts sent by link open without an account and without an app, branded in your colours, optionally protected by an emailed code. One click to view, one click to sign — fewer hurdles, more acceptances.
  • Sign by drawing, typing or uploading a PDF — stored as a plain image, never as a graphics file that could hide malicious code
  • Proof with IP address, device and a checksum of the signature; optionally with an emailed code
  • A rule turns the quote acceptance into the order; the contract signature updates the revenue
  • Your customer downloads quotes, orders, invoices and contracts as a PDF in the portal and via the document link — the same PDF from the server as yours, never a draft
  • Links in a document email point to the customer address of your portal — to your own domain as soon as one is set up

Support and documents in one place 7

  • View invoices, report a payment Your customer finds their invoices themselves at any time and reports a payment they have made with one click. The report arrives with you as an open item for internal confirmation — an end to “did you receive my transfer?” emails.
  • Support in a real-time chat Instead of email chaos, the customer raises a ticket and chats live with your team — with typing indicators, an unread counter and a complete history. Once the matter is resolved, a short satisfaction survey goes out if you want it — as its own branded link by email, not as a portal page.
  • Documents in both directions Share documents selectively — and let the customer upload files themselves. Every customer upload is flagged to you as “new” and mirrored into your central storage, in the folder of the respective company. No more emailing attachments back and forth.
  • Tickets with status, ownership and live chat (typing indicator, unread)
  • Resolved tickets can trigger a satisfaction survey — as its own emailed link, not in the portal
  • Documents in both directions: releases from you, uploads from the customer
  • A file already in your storage you link as a portal document instead of uploading it again

Security, roles & payments 10

  • GDPR data export, self-service Your customer pulls their own data as a branded PDF or JSON — account, company, consents, documents, tickets, activity. Data subject rights become a built-in button instead of a manual special task on your desk.
  • Portal roles across eight areas (quotes, orders, invoices, contracts, documents, tickets, payment history, profile)
  • Password policy, lockout after failed attempts, central session management
  • Payment is only reported and confirmed internally — never collected in the portal
  • A statement of account, over a period you choose Your customer picks a period and sees every document in it — paid, open, overdue, part-paid, reported or cancelled, each with its total. Printing works straight from the view, without anyone on your side assembling a list.
  • Their own numbers, in the portal A small analysis inside the portal: paid volume, open and overdue invoices, quote volume — with the lists behind them. The same numbers you see on the inside, narrowed to this one customer.
  • Security events with a risk level (low to critical), filterable by person and by kind
  • Access that only counts once the email has really gone out You create portal customers, change them, switch them off or back on. An invitation counts as sent only once the email has demonstrably been delivered — and when you send it again, the old link is invalidated only afterwards, so nobody is left between two dead links.
  • A single system email — welcome, password reset — you send deliberately by hand
  • An account you reset completely: every session ends, and a fresh invitation goes out at once if you want

What you set on the portal 5

  • Switch areas off entirely, not merely hide them You decide per workspace which areas exist in the portal at all. That is a different thing from the roles: those govern WHO sees something — here you decide whether the thing is in the portal. What is off appears in no navigation either.
  • Your own portal roles, four rights per area Beyond the roles that ship with the app you create your own, rename them and delete them. Per area you grant read, create, change and delete separately — not one switch for everything.
  • How your support appears in the chat You decide whether the customer sees the real name and picture of the person handling the case, or a shared display name. That way it is your team in the window, not an individual.
  • Internal notes on a ticket: stored in the same thread, invisible to the customer, with no notification to them
  • Resolved tickets close themselves after a deadline you set — if the customer comes back first, they stay open
The neighbours

The module before, the module after

All 21 sit in a fixed order — from here it continues in both directions.

Customer portal is module 5 of 21 — the same order as in the menu and the footer.

One message at launch. After that you'll find me in the top right of the app.

Customer portal is one of 21. You get all of them.

Sign up and you'll hear from us the moment we go live. Not a newsletter — one message.

€50€150/ month · permanently

Waiting list

Only your email address. No spam, unsubscribe at any time.

See all modules

€50€150/ month · permanently

50 founder placesTell me when it starts