Blog
Practical guides, pricing teardowns, and the occasional opinion piece. Written for founders, ops people, and IT admins who care how their email actually works.
A concrete recipe for routing incoming invoices automatically: match by sender domain, extract the PO number with a snippet, and push to your ERP via webhook — all inside Biza's automations engine.
The +tag trick turns a single mailbox into thousands of disposable, filterable, leak-detecting addresses — and it works without you configuring anything.
Catch-all addresses and role aliases both have a place in small-team email. Here is how to decide which to use — and when you might want both.
Building a global SaaS sounds like a problem of translation and timezones. The actual surprises are deliverability quirks, bank-transfer expectations, local DNS registrars, and customers asking 'can I pay in my currency'.
Per-seat pricing is a hangover from Microsoft Office. Email doesn't behave the way per-seat priced things behave. Here's the short version of why we picked a different model.
The sticker price is per user per month. The actual cost includes ex-employees, role addresses, storage upgrades, and the things you stop doing because the math gets uncomfortable. Here's the unbundled view.
Role addresses look simple. Most teams set them up as alias-to-one-person and then watch them quietly stop working. Here are the three patterns, when to use which, and the operational habits that keep them alive.
If your team is using passwords for email, you have a problem you'll discover at exactly the wrong moment. Here's the SSO-first alternative — what it changes day to day and why it pays for itself the first time someone leaves.
When mail mysteriously lands in spam, when a sender swears they replied but you don't see it, when a forwarded message gets stripped — the answer is always in the headers.
A day-by-day playbook for moving team email off Google Workspace without losing mail, breaking deliverability, or paying a migration consultancy.
Three records, three jobs. A practical tour with the exact DNS lines you'll publish — and the order to adopt them in without breaking deliverability.