Our work
Everything on this page can be checked: the tools and open-source projects we have built are live and public, the project steps are the scope we put in our quotes, and the deliverables are anonymised templates marked “Sample”. We do not show client names, logos or testimonials without written permission.
What we've built (check it yourself)
Free tools for the same work we do for clients: DNS, email authentication, Microsoft 365 change tracking and cloud costs. Use them on your own domain or tenant before you talk to us.
DNS lookup
Look up A, AAAA, CNAME, MX, TXT, NS, CAA and SOA records for any domain, with TTLs and a share link.
Email domain checker
Check MX, SPF (with the 10-lookup limit), DKIM, DMARC, MTA-STS and TLS-RPT for any domain, with fixes.
DMARC record generator
Build a DMARC record step by step, from p=none monitoring to p=reject, with reporting addresses.
Email security score
Grade any domain A to F on MX, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, BIMI and DNSSEC, with the risk and a sample record for every fix.
Make.com credits calculator
Estimate the Make credits your scenarios use a month, with polling checks shown separately, a peak month, a safety margin and the plan that fits.
Cloud cost optimizer
Upload an Azure or AWS cost export and get explainable savings: reservations, idle disks, dev/test schedules, storage tiers and more. The file never leaves your browser.
Microsoft 365 retirement calendar
Upcoming Microsoft 365, Teams, Exchange, Entra, Intune and Azure retirements and deadlines, each with what changes, what to do and the official source. Subscribe by calendar (ICS) or RSS.
Service status hub
Live status for 12 services, including Microsoft 365, Outlook, Teams, Azure, AWS and Google Workspace, read from each vendor’s official status feed.
Products
EpiFive DMARC Monitor
DMARC aggregate report monitoring for small businesses and IT teams: see who sends email as your domain, fix SPF/DKIM failures, and move safely from p=none to p=quarantine/reject.
EpiFive Mail Merge for Outlook
Personal emails to your whole list, sent from your own Outlook. Upload an Excel or CSV list, write one message with {{First Name}}-style fields, preview every row and send. Free for 50 emails a day.
Open-source projects
11 MIT-licensed apps with their full source code on GitHub, under the epifive organisation, so you can read exactly how we build software.
- Statuszen: Uptime monitoring, public status pages and cron job monitoring you host yourself.
- Pulsezen: Cookieless, privacy-friendly website analytics: a Google Analytics alternative you host yourself.
- Trustzen: Social proof, testimonial and conversion widgets you host yourself.
- Referzen: Affiliate and referral program software you host yourself.
- Searchzen: SEO rank tracking, site audits and client reports you host yourself.
- Queuezen: A social media scheduler you host yourself: plan, approve and publish on 10 networks.
- Dialzen: AI voice agents for inbound support, appointment booking and consented follow-ups.
- Toolzen: An all-in-one online tools website you run yourself: 156 tools, plans, ads and a blog.
- CRM for WhatsApp: A WhatsApp CRM with a shared team inbox, contacts, deals, chatbot flows and an AI assistant.
- EpiFive GST Invoice: A GST invoice, quotation and receipt maker with UPI QR that runs entirely in the browser.
- EpiFive QR Code Generator: A styled QR code generator for UPI, WiFi, vCard and links that runs entirely in the browser.
Checklists and guides
- 6 printable checklists and kits (168 items in total), each item linked to the vendor documentation it comes from: Microsoft 365 security, a new-tenant baseline, Google Workspace to Microsoft 365 migration, Azure cost saving, an AI use policy kit and device buying.
- 13 command cheat sheets for Exchange Online, Microsoft Graph and Active Directory PowerShell, Azure CLI, network devices and more.
- 601 step-by-step articles, each listing its sources. How they are researched, written with AI assistance and corrected is in the editorial policy.
How a project runs
A typical Microsoft 365 migration with email security, for example moving a small office from Google Workspace. These are the steps and terms we put in writing in every quote. A small office usually goes from approval to cutover in one to two weeks; DMARC enforcement then follows over about 60 days.
- Assessment . Users, shared mailboxes, mailbox sizes, aliases, groups, delegated access, the DNS host and every service that sends email as your domain. You get a written scope and a fixed-price quote, with what is excluded spelled out.
- Pre-staging . Accounts and mailboxes prepared in Microsoft 365, existing mail history copied in the background while everyone keeps working, DNS TTLs lowered, and SPF and DKIM prepared for the new service.
- Written rollback plan . What would make us roll back, who decides, how mail routing is restored and how mail received in between is kept. You sign off on it before anything is switched.
- Final sync and after-hours cutover . The MX switch outside your business hours at a time you choose, then a final synchronisation so mail that arrived during the change is not missed.
- MFA verification and testing . Every user signs in with MFA, mail flows in and out, shared mailbox permissions and Send As work, calendars and contacts are present, and item counts are checked against the source.
- 14 days of support . A short guidance session for staff, then help with anything that does not look right: Outlook profiles, phones, rules, missing items. Business hours, next-business-day response.
- DMARC staged to enforcement . DMARC starts at p=none with reporting, then moves to quarantine and reject as the reports show your legitimate mail passing. You approve each policy change.
Sample deliverables
Anonymised templates of what you receive. They are samples, not work for a real client: names, numbers and dates in square brackets are filled in for each project, and example.com stands in for your domain.
Sample migration plan outline
- Scope and inventory. [N] user mailboxes, [N] shared mailboxes, sizes, aliases, groups, delegated access. What is in scope and what is not.
- Approach and tools. Migration method and tooling for each type of data, and anything that has to be rebuilt by hand.
- Timeline. Start date, pre-staging window, cutover date and time in your time zone, support end date.
- What users will notice. What changes for each person on cutover day, and the one-page guide they receive.
- Access and approvals. The admin roles needed, for how long, and who on your side approves each change.
- Email security. SPF, DKIM, DMARC, MTA-STS and TLS-RPT changes, with the DMARC schedule below.
- Rollback plan. Triggers, decision owner, the steps to restore mail routing, and how in-between mail is kept.
- Acceptance tests. The checks that mean "done": sign-in with MFA, mail flow, permissions, item counts.
- Handover. Change log, final configuration notes, removal of our access and the support contact.
Sample cutover checklist
- Rollback plan signed off; source data and admin contacts confirmed
- DNS TTLs lowered at least 24-48 hours ahead
- Incremental sync run and checked the day before
- Cutover: MX, Autodiscover and SPF switched at the agreed time
- Final sync after DNS changes, then test mail in and out
- Every user signed in with MFA; desktop and phone Outlook checked
The full version we work from is public: Google Workspace to Microsoft 365 Migration Checklist (PDF, 32 checks), and the email cutover checklist explains each step.
Sample DMARC rollout schedule
| When | Record | What happens |
|---|---|---|
| Day 0 | v=DMARC1; p=none; rua=mailto:[email protected] | Monitoring only. Aggregate reports start arriving within a day or two. |
| Days 1-21 | no change | Reports reviewed; every legitimate sender identified and fixed for SPF (10-lookup limit) and DKIM alignment. |
| About day 21 | v=DMARC1; p=quarantine; pct=25; rua=... | Failing mail starts going to junk, for a share of messages first. Only with your approval. |
| About day 35 | v=DMARC1; p=quarantine; rua=... | Quarantine for all failing mail, if the reports stay clean. |
| About day 45-60 | v=DMARC1; p=reject; rua=... | Enforcement: mail that fails DMARC is refused. A final report and handover follow. |
Sample email security report
One row per check: what we found, why it matters and the exact fix, with who on your side acts on it.
| Check | Finding | Fix |
|---|---|---|
| DMARC | [Record found, e.g. p=none] | Policy step and date, from the schedule above |
| SPF | [Lookups used of 10, senders missing] | The corrected record to publish |
| DKIM | [Selectors found, alignment] | Signing to enable, per sending service |
| MTA-STS / TLS-RPT | [Present or missing] | Policy file, DNS records and report address |
How we handle your data
Least-privilege, time-boxed access
Only the admin roles the work needs, read-only wherever the platform allows it, for the dates of the project, on accounts protected with MFA. When the work is done the access is removed, and you can confirm that in your own admin centre.
An NDA on request
We sign an NDA before the assessment if you ask for one.
No copies beyond what the migration needs
Mail and files move from the old service to the new one with the migration tooling. Nothing is copied to our own systems beyond what the migration itself needs, and your data is used only for the engagement.
A written change log
Every setting changed, with the date, the reason and who approved it, delivered at handover so your team or your next provider can see exactly what was done.
How we price
- A fixed-price quote after the assessment, itemised, with exclusions listed. No hourly billing surprises.
- 50% on approval, 50% on completion.
- Each quote is valid for 30 days.
- If the assessment turns up more data or work than quoted, we re-quote before that work starts.
- Microsoft 365 licences are billed by Microsoft or your reseller, separately.
Every environment is different, so there is no public price list. See what each service includes on the services page.
Case studies
We publish case studies only with the client's written permission, after a project is complete. They will appear here as they are approved. Until then, everything above is what we can show without breaking anyone's confidentiality.
Request a quote
Tell us roughly how many users and mailboxes you have, where your email is today and when you would like to switch. You get a written scope and a fixed-price quote; we reply within 1 business day.