The Series· No. 37 · Act IX — The Foundation

By DocuSeller · Published

The Foundation
DocuSeller · No. 37

Everybody's name over the door

Every management company on DocuSeller gets its own site, its own logo, its own web address.

There is exactly one application.

It works out whose name to wear from the address you typed.

Four software crates carry version labels, with a bug confined to the third version Copies drift apartv1v2v3v4Different versions. Different failures.
Nine copies. Four versions. One bug that lives only in the third crate.

The old way is to hand every customer their own copy of the software.

That works beautifully for about eleven months. Then you have nine copies, four versions, and a bug that only exists in the building on the corner.

So: one building, many tenants. Two levels of them.

A company sits at the top. Its communities sit underneath. Each company owns its own associations, units, packages, orders, staff, roles and fees — and none of it is visible from next door.

One application. Everybody's name over the door.
A single application doorway carries one resolved company sign while alternate brand signs remain separate One application, each company’s identityCompany ABrand BBrand CBrand DBranding follows the requested site address
The building doesn't change. The board over the door does.

Branding is decided the moment the page loads. A path prefix, or a full custom domain, and the storefront resolves the right logo, title, contact details and search metadata before it paints anything.

An unresolved site shows a neutral storefront instead of another company’s identity When the site is unresolvedNeutralstorefrontAnothercompanyShow a plain identity when unknown
If it can't tell whose site this is, it wears nobody's name. Never the wrong one.

If it can't work out whose site this is, it falls back to a plain, unbranded one.

Then the genuinely hard part: the custom domain.

A company wants documents dot their-own-name dot com. Their brand, their address, no mention of us anywhere in it.

Doing that once is a support ticket. Doing it for every customer, forever, is a department.

So it's self-service. A wizard walks them through pointing the address at us. The platform binds it, verifies it, and the certificate — the little padlock in the browser bar — is issued and renewed automatically.

No engineer. No Saturday where the padlock quietly expired.
Custom-domain setup points the address, verifies the binding, and manages certificate renewal Connect a company domainPoint DNSSet addressVerifyBind domainSecureAuto renewal
Three screens for them. No calendar reminder for anybody.

Last piece, and it's the least glamorous idea in the whole product: settings that know where they live.

Platform, company, and community settings nest by scope with inheritance unless a specific override is configured Settings have a scopePlatformCompanyCommunitySpecific overrideInherit unless an override is configured
Building rules, floor rules, room rules. The smallest room wins.

Payment keys sit at the top. Branding sits with the company. Campaign defaults sit with the individual community.

One mechanism, three altitudes. Set once, overridden only where somebody actually cares.

White-labelling demos in ten seconds. Here's your logo, sir.

Operating it is the product.

Next: the one missing word that would be the worst thing we could ever ship.

#PropTech · #SaaS · #HOA