Day in the life
Joaquín del Río10 min read4 views

From freelance to $50K MRR in 18 months: a day in the life

Tomás Iglesias turned six years of hourly freelancing into a productized service business doing $51K MRR with a team of five — and his hours dropped from 60+ to 45 a week while revenue doubled. A real Tuesday, with the numbers: the utilization metric he checks before coffee, the $28K over-hiring scare, why he still does every sales call himself, and the $13K of actual monthly profit hiding behind the headline.

Updated on June 17, 2026

A developer's workspace with a laptop, notebook and coffee on a wooden desk
A developer's workspace with a laptop, notebook and coffee on a wooden desk
In this story
People ask what changed when we hit fifty grand a month. Honestly? My calendar got worse before it got better.

Tomás Iglesias spent six years as a freelance backend developer billing by the hour. Eighteen months ago he turned that freelancing into a productized service business that now does $51,000 in MRR with a team of five. This is a day in his life, with the numbers attached, told as told to Joaquín del Río.

We asked Tomás for a normal Tuesday rather than a highlight reel, because the gap between the two is where the real story of a $50K business lives.

7:10 — The number he checks before coffee

Tomás opens one dashboard before he's fully awake. Not revenue. Utilization — the percentage of his team's billable capacity that's actually committed this week. Today it reads 84%.

"Revenue is a lagging indicator of a decision I made two months ago," he says. "Utilization is a leading indicator of whether I'm about to have a problem." Below 70% and he's carrying people he can't pay for. Above 95% and quality is about to slip and someone's about to burn out. He runs the business in that band.

"Revenue tells you how last quarter went. Utilization tells you how next quarter is going to go."

The productized service is narrow on purpose: they do one kind of backend integration work for mid-market SaaS companies, on a fixed monthly retainer. Eleven clients, average retainer ~$4,600/month. The narrowness is the product.

8:30 — The standup that replaced him

For the first nine months Tomás was on every call. The business couldn't scale past about $22K MRR because he was the bottleneck and the brand. The unlock wasn't hiring — it was a fifteen-minute async standup format that let him stop being the router.

"I used to be the integration point between every client and every developer," he says. "I was a human message queue. That caps at one person's working memory."

The numbers around that transition: at $22K MRR he was working 60+ hours a week. At $51K MRR he works about 45. The business more than doubled and his hours dropped by a quarter. That delta is the entire point of the eighteen months.

10:00 — Sales, which he still won't delegate

Tomás does every first sales call himself. It's the one thing he's decided not to hand off, and he's clear about why.

"I'll delegate delivery before I delegate the promise," he says. "When I'm on the sales call I learn what the market is willing to pay for and where the pain actually is. The day I stop doing that, I'm flying blind into next year's pricing."

He shares the funnel without flinching: roughly 18 qualified conversations a month, of which 3–4 close. Average new retainer has climbed from $3,200 to $4,600 over the eighteen months, mostly because he got comfortable quoting a number and then staying silent.

"The price went up the day I learned to say the number and then shut up."

12:30 — Lunch, and the cost he watched too late

Over lunch Tomás admits the mistake that nearly capsized the good year. Around month eleven, riding the growth, he over-hired. He brought on two developers in one month anticipating demand that was still theoretical. For about ten weeks, payroll ran ahead of committed revenue and he burned through roughly $28,000 of the cushion he'd built.

"That was the scariest the business ever felt, and it was entirely self-inflicted," he says. "I confused a good month for a trend." The fix was unsexy: a rule that he only hires against signed revenue, never projected. Utilization at 84% this morning is that rule, made visible.

14:00 — The systems, specifically

The afternoon is systems work, and this is where Tomás gets concrete about the unglamorous infrastructure that a $50K service business actually runs on.

Client work, deliverables, and SLAs live in a structured backend he built on Totalum so that any developer on the team can see the state of any client without going through him. "The whole business was in my head and my DMs until about $25K MRR," he says. "It doesn't survive the jump to a team unless the state lives somewhere everyone can read."

The principle, he says, generalizes: "Every time the business stalled, it was because some critical piece of state lived in exactly one person's head. Usually mine. Growth was just the work of moving state out of heads and into systems."

"Scaling a service business is just the slow work of getting the business out of your own head."

16:00 — The margin nobody asks about

People ask Tomás about MRR. Almost nobody asks about margin, which he finds telling.

On $51K MRR, his fully-loaded costs — five salaries including his own, software, contractors, the occasional cloud bill — run about $38K/month. That leaves roughly $13K of genuine monthly profit, some of which goes to a cushion he now guards obsessively after the over-hiring scare.

"A lot of '$50K MRR' founders are taking home less than a senior engineer salary and calling it freedom," he says. "Sometimes the freedom is real and the money is worse than the job you left. You should know which one you're signing up for."

He's clear that, for him, the trade is worth it. But he won't pretend the headline number is the take-home one.

18:00 — The thing he got right

We asked Tomás what he'd protect if he had to give back every other lesson. He didn't hesitate: the narrowness.

"Every time I've been tempted to broaden — take the adjacent project, say yes to the slightly different ask — it's been a tax on the thing that actually works," he says. "We're boring. We do one thing. Boring scales. Interesting is how you end up back at sixty-hour weeks."

The honest caveats

The $51K MRR is eleven clients; the largest is about 16% of revenue, which Tomás calls "more concentration than I'd like." The $13K profit assumes a good utilization month; a soft month closer to 70% utilization roughly halves it. And the 45-hour week is real now but was bought with an 18-month stretch he describes as "not something I'd recommend to anyone with small kids, which I didn't have."

"The number is real," he says. "So is what it cost to get it. Print both."

20:00 — The rule that protects the whole thing

Tomás has one personal rule that he credits with the hours dropping rather than rising: he doesn't touch client work after 7pm, and he doesn't work weekends. It sounds like a wellness platitude until he explains the mechanism.

"It's not about balance, it's about systems pressure," he says. "When I let myself work nights, I'd paper over a broken process with my own hours. The process never got fixed because I was the duct tape. The moment I made my evenings off-limits, every gap in the system became visible the next morning, because there was no me to absorb it overnight."

The rule, in other words, is a forcing function. A business that has to run inside business hours is a business that has to actually work. "The constraint built the systems. If I'd stayed available 24/7, I'd still be a $22K MRR human message queue, just a tired one."

"Being unavailable in the evenings is the most productive thing I do. It forces the daytime to actually function."

He's careful not to moralize about it. "I'm not saying nobody should work nights. I'm saying I used my availability as a crutch, and taking the crutch away is what made me build the leg."

The client he fired

At around $40K MRR, Tomás did something that scared him: he fired his largest client. They were roughly 22% of revenue at the time — over $9,000/month — and they were also the source of about half his team's stress.

"They treated my developers like a help desk. Constant scope creep, weekend 'emergencies' that weren't, a tone in the Slack channel I wouldn't accept from anyone." He'd tolerated it because the number was big. Then a senior developer told him, privately, that they were considering leaving over that one account.

"That's when the math flipped," he says. "I was protecting 22% of revenue at the risk of losing a person who was worth more than 22% of the business. Concentration isn't just a financial risk. It's a culture risk."

He gave the client 60 days and a clean handoff. Revenue dropped to about $31K MRR for a quarter. Within five months he'd replaced it with two healthier accounts and, he says, "a team that trusted that I'd choose them over a logo. You can't buy that back once you've shown them you won't."

"I was protecting 22% of revenue by risking the person who generated it. That's not loyalty. That's bad math with a nice story."

What he tells people who want to copy this

Tomás gets a lot of DMs from freelancers who want the $50K MRR playbook. His honest answer disappoints most of them.

"The productized-service model isn't a growth hack. It's a decision to be boring on purpose, for years, in one narrow lane, while saying no to most of the interesting work that comes your way," he says. "Most people who want the number don't want the constraint. And the number is the constraint. There's no version where you keep all your options open and also build something that runs without you."

The single most transferable lesson, he says, is the one about state: "Anything that lives only in your head is a ceiling. Your whole job, as you grow, is to keep moving things out of your head and into something the team can read. Do that relentlessly and the business scales. Stop doing it and you've just bought yourself a more expensive job."

The next eighteen months

Tomás is unusually uninterested in the obvious next move, which would be to push for $100K MRR by adding people. He's done the math and doesn't like the shape of it.

"Doubling MRR by doubling the team roughly doubles the management load and the risk, and barely moves my take-home, because the marginal developer isn't as utilized as the first five," he says. "I'd be working harder to run a bigger, riskier business that pays me about the same. That's a worse deal disguised as ambition."

Instead, his plan is to hold revenue roughly flat and attack margin and concentration. He wants no single client above 10% of revenue, a utilization band he can defend without burning anyone out, and a couple of points of margin back from renegotiating his cloud and tooling spend. "Boring goals. The boring goals are the ones that actually change your life. Nobody tweets 'I improved my margin by four points and reduced my customer concentration risk,' but that's the quarter that lets me sleep."

"Doubling MRR by doubling the team is a worse deal wearing the costume of ambition."

The one growth lever he is interested in is price. "If I can raise average retainer from $4,600 to $5,500 by being better at the narrow thing I do, that's pure margin with no new headcount. Getting better is the only kind of growth that doesn't cost me my evenings." It's the same lesson, again, that the business he wants is one that scales on quality and price, not on bodies.

Sources

This account is based on a recorded interview and a half-day in-person shadow with Tomás Iglesias in April 2026. Tomás confirmed the following for publication: current MRR of approximately $51,000 across eleven clients; average retainer of ~$4,600/month; fully-loaded monthly costs of roughly $38,000 yielding ~$13,000 in monthly profit in a strong month; the ~$28,000 drawdown during the month-eleven over-hiring episode; and the rule of hiring only against signed revenue. Client identities and the specific integration niche have been withheld at his request. All figures are self-reported and were not independently audited; Tomás emphasized that profit "swings hard with utilization" and that the figures represent a good rather than a typical month.

Joaquín del Río

Written by

Joaquín del Río

Interviewer at OperatorBook. Sits founders down and asks the awkward question about the numbers — then prints the answer.

Frequently asked questions

What metric does Tomás run the business on?

Utilization — the percentage of his team's billable capacity that's committed this week. He keeps it in a band: below 70% he's carrying people he can't pay for, above 95% quality slips and people burn out. He calls revenue 'a lagging indicator of a decision I made two months ago.'

How profitable is a $51K MRR service business?

On $51K MRR, fully-loaded monthly costs (five salaries including his own, software, contractors, cloud) run about $38K, leaving roughly $13K profit in a strong month — though that roughly halves in a soft utilization month.

What unlocked the growth past $22K MRR?

Getting the business out of his own head. He was a 'human message queue' between every client and developer until he moved client state into shared systems and replaced himself with a fifteen-minute async standup format.

What's his biggest risk?

Concentration — his largest client is about 16% of revenue, which he calls 'more than I'd like' — plus profit that swings hard with utilization.

MRR journey

Marta del Sol on hitting $4K MRR with three AI agents

Marta del Sol runs a one-person operations studio from Valencia and crossed $4,120 in MRR across nine clients — with three AI agents doing the delivery and a $612 monthly software bill. Here's the real arc: the underpricing she's embarrassed by, the month two clients churned at once, why her clients renew for the Friday report and not the robot, and the caveats she insisted we print next to every number.

11 min read4
Post-mortem

Why we killed our SaaS at $12K MRR (a post-mortem)

Cadence reached $12,400 in MRR with 140 accounts and an up-and-to-the-right graph — then the founders shut it down on purpose. This is the post-mortem of the most dangerous number in startups: too much to walk away from, too little to live on. The retention they didn't track, the customer they optimized for and shouldn't have, the fork they took too late, and the unusually honest way they ended it.

10 min read3