About a year ago we published a post introducing DogHouse, our client portal. It was a short, frankly overcooked announcement that did not really explain what we had built or why. This is the post I should have written then, now that DogHouse has a year of real use behind it and a brand new version to go with it.
Here is the short version. DogHouse is software we built ourselves, from scratch, to run FatLab. It is the portal our clients log into, and it is also the system we use to run the entire business behind the scenes. As of this week it is on version 2.0, rebuilt around our new brand. Let me walk through what it is, what changed, and the parts you have probably never seen.
A quick word on the new look
If you read our recent post about FatLab's new look, DogHouse 2.0 is that same story applied to our software. We retired the old dark theme and rebuilt the interface as a lighter, cleaner, more corporate-friendly design. New logos, the new color palette, and the new typography (Montserrat and Inter) now run through every page, and even the emails DogHouse sends you.
Version 2.0 is more than a coat of paint, though. We rebuilt the styling on a modern design-token system, which is a developer way of saying the whole interface now pulls from one consistent set of colors, spacing, and type rules. That makes future updates faster to ship and keeps everything looking the same from screen to screen. The feature set is largely what it was last week. This release was about the look and the foundation underneath it.
DogHouse even has its own logo now: a doghouse with the same Labrador that anchors the FatLab brand. It is part of the family.
What DogHouse actually is
Most web hosts hand you a generic control panel, usually something off the shelf with their logo on it. DogHouse is not that. We did not buy it, license it, or rebrand someone else's tool. We wrote it, line by line, for the specific way FatLab works with clients.
That distinction matters. It means DogHouse fits our process instead of forcing our process to fit a piece of software. When we change how we do something, we change the tool to match. When a client asks for something reasonable, we can often just build it.
It has two sides. The side you see is the client portal. The side you do not see is the back office that runs our company, from a brand-new sales lead all the way through to a paid invoice and an answered support ticket. Both run on the same system.
The client side: what you see when you log in
This is the part built for you. If you are a FatLab client, here is what is waiting when you log into DogHouse, and honestly, some of it may be news to you.
Your dashboard. A single overview of your account: open tickets, billing status, your sites, and anything we have flagged for your attention. It is the front door to everything else.
Support tickets. Every request you have ever sent us, in one place, with the full conversation, current status, and any file attachments. You can open a new ticket or reply to an existing one right from the portal. And because DogHouse is wired into our email, you can also just reply to us by email and it lands in the same thread. No more digging through your inbox wondering where things stand.
Uptime monitoring. We watch your site around the clock, and you can see it too: whether your site is up right now and its uptime history over time. If something goes down, we usually know before you do.
Traffic and page views. A simple read on how much traffic your site is getting, without logging into a separate analytics platform.
Invoices and payments. Every invoice and payment in your history, viewable and downloadable as a PDF. You can pay by card, save and manage payment methods, and handle recurring billing right there. For clients on custom development work, you can also see time tracking, exactly how the hours are being spent.
Your hosting details. The servers and applications behind your sites, laid out in plain terms.
If you have never clicked into all of that, it is worth a look. Plenty of clients use DogHouse for tickets and invoices and never realize the uptime and traffic data is sitting right there.
The back office: the part that runs the company
Here is where I get to show off a little, because this is the part nobody outside FatLab ever sees, and it is the part I am proudest of. DogHouse does not just give clients a window into their account. It runs the entire business.
Leads and the sales pipeline
Everything starts with a lead. When a potential client reaches out, they enter our sales pipeline, a visual board where we track every prospective deal from first contact through to a signed client. We log calls and activities, set reminders so nothing slips, and run reports on where our new business is coming from.
Companies and contacts
Once someone becomes a client, they get a company record: their organization, their contacts, the websites we manage for them, the servers and applications those sites run on, and the documents tied to the relationship. It is the single source of truth for who everyone is and what we run for them.
The ticket system
This is the engine that probably matters most, day to day. When you email us, DogHouse turns that email into a ticket automatically, routes it, and keeps the whole conversation organized. We group related work into projects, track time against it, flag tickets that have been waiting too long for a reply, and send you confirmations and updates along the way. The same system that shows you a tidy list of your requests is, on our end, a full support desk.
Billing and financial reporting
Billing runs through DogHouse too. We generate invoices as PDFs, handle recurring billing and subscriptions through Stripe, track the specific charges and plugins tied to each client, and process payments. And because we run the whole business here, we built a real financial reporting layer on top of it: upcoming revenue forecasting, a twelve-month cash flow forecast, invoice aging so we always know what is outstanding, a revenue intelligence dashboard, and even a financial health score that grades the business from zero to one hundred on a handful of key metrics.
Hosting, email, and expenses
On the infrastructure side, DogHouse connects to our hosting platform so we can see and manage the servers and applications we run for clients without leaving the system. Our client emails go out through a templated, on-brand communication system. We even track our own company expenses in here. From a brand-new lead, to a paid invoice, to a resolved support ticket, it is all one system.
A year of building it for real
The reason I can write all of this with a straight face is that DogHouse is not a demo or a side project. We have run FatLab on it every single day for almost a year.
We launched version 1.0 in the summer of 2025. In the year since, we shipped more than 180 updates across the 1.x series before this 2.0 rebrand, everything from small bug fixes to whole new features. Some of those came from our own daily use, where we hit a rough edge and smoothed it out. A good number came from clients who took the time to tell us what was confusing or what they wished it did. We genuinely appreciate that feedback, and a lot of it is now baked into the product. Thank you.
That is the part I want to land. Software gets good by being used and refined, not by being launched. A year of running our actual business on DogHouse, with real money and real client work flowing through it, is what turned it from a thing we built into a thing we rely on.
Why we built our own
We could have stitched together a CRM, a help desk, a billing tool, and a hosting dashboard from four different vendors and spent our days getting them to talk to each other. Plenty of agencies do exactly that. We went the other way and built one system that does all of it, shaped around how we actually work.
I will be straight about what DogHouse is and is not. Today it is not a product you can buy. There is no signup page and no pricing tier. It is a value-add, included for the clients who work with us, and a serious operational tool for us. Could it become a real product someday? Maybe. We build it, version it, and maintain it like one. But right now its job is to make working with FatLab clearer for you, and to keep our business running tight on our end.
If you are a client, log in and poke around. There is more in there than you probably realize. And if you find something that would make it better, tell us. That is how it got this far.