Bespoke work: a lettings platform that carries your brand, not ours

There is a moment in every agency’s software evaluation where somebody asks what the landlord will actually see. It is a better question than it sounds, because the answer determines whether the tool makes the agency look more capable or merely more outsourced.

A monthly statement arriving from an address the owner does not recognise, with a logo they have never seen, does not read as modernisation. It reads as: my agent has handed my portfolio to someone else. That perception is expensive, and it is entirely avoidable.

The three surfaces that reach your clients

Most of the work in a white-label engagement is not the app your staff use. It is the three places your name appears in front of somebody who is not your staff.

Branding the first two is largely a matter of configuration: your wordmark, your colour, applied through the portal shells and the PDF templates, with a live preview so you can see the statement and the email as the recipient will before anything goes out. That part is quick.

The part that is actually engineering: sending as you

Email is where most white-label claims quietly stop. The logo changes; the sender does not. Mail still leaves as no-reply@somevendor.com, and every recipient’s mail client says so.

Sending genuinely as the agency is a deliverability problem before it is a branding one. Modern mail providers authenticate the sending domain: if the envelope claims to be your agency and the cryptographic signature says otherwise, the message is treated with suspicion or dropped. You cannot fake it, and you should not want to — the same mechanism is what stops other people sending as you.

The onboarding cost to you is “add three DNS records”, which is the same thing you have already done for every other tool that sends on your behalf. What you get back is that no correspondence in the entire product carries a vendor’s name, and that your deliverability is your own reputation rather than one shared with every other customer of a platform.

The one place branding must not go

Statutory notices stay unbranded, and this is a deliberate line we will not move for a customer who asks.

A Section 8 notice, a Section 21 where still applicable, a Form 4A — these are prescribed documents. Their validity rests on being in the prescribed form or “substantially to the same effect”. A wordmark printed across a served notice is an argument you have handed to the other side’s solicitor for no benefit whatsoever, in a document whose entire purpose is to survive scrutiny.

So branding flows through the covering email, the statements, the portals and the reminders — everything that is correspondence — and stops at the legal document itself. The covering email absolutely should come from you. The notice inside it should look exactly like the notice the court expects.

What a bespoke engagement looks like

The configurable parts — brand, portals, sending domain, fee arrangements, notification routing, per-branch access — are set up rather than built, and that is usually a matter of days. Where the work becomes genuinely bespoke is the edges: a statement layout an institutional owner requires in a particular shape, a reporting obligation inherited with an acquired book, an intake route from a system you are not replacing yet.

Those we scope individually, and we would rather tell you which of them is a configuration, which is a build, and which is something we do not do, than discover it together after a contract is signed. If you have a list, send it to hello@tekniti.ai and we will mark it up honestly.