Dublin Startup’s Single 45-Minute Meeting Cuts Churn and Boosts Focus

The kettle has just boiled on the third floor of a converted warehouse on Sir John Rogerson's Quay when Cian Molloy walks in carrying a single sheet of A4 paper. On it, handwritten in blue biro, are four bullet points. He sets the paper on the long oak table at the centre of the room and pours himself tea. It is 8:47 a.m. on a Wednesday in late April. By 8:52, thirty-seven people have filtered in. Some sink into the mismatched sofas near the window overlooking the River Liffey. Others perch on stools dragged from desks. A handful stand near the kitchenette, nursing coffees. No laptops are open. This is the only all-hands meeting of the week at Keel, a Dublin payments infrastructure startup, and it will last exactly forty-five minutes.

Keel employs fifty-two people now, small enough that every new hire still changes the shape of the company, large enough that Molloy can no longer name every partner of every employee. The company occupies what estate agents call a mid-stage startup: post-Series B, pre-profit, burning a careful €380,000 a month. In an industry that fetishises speed, Molloy has built a company around a deliberately slow internal rhythm. Mondays and Fridays are meeting-free. Tuesday holds one-to-ones and customer calls. Wednesday carries the single all-hands. Thursday is reserved for sprint reviews and product demos. The structure has been in place for eighteen months. Depending on whom you ask, it is either the reason Keel retained 94 percent of its engineering team this year or a quiet source of friction that nobody has yet named aloud.

Molloy arrived at this cadence the way many founders do: by shattering the opposite one first. In Keel's first two years, from 2021 to early 2023, the company ran what he now calls a 'default startup schedule,' which meant, in practice, no schedule at all. Standups happened whenever someone remembered to call them. Product reviews bled into engineering discussions, which bled into hiring panels. Calendar Tetris was a daily sport. By December 2022, a staff survey returned a number that stopped him cold: the thirty-one employees were spending an average of nineteen hours a week in meetings. Molloy is thirty-eight, a former Stripe engineer with a quiet intensity. He speaks with the trace of a Kerry accent he has mostly trained himself out of, and he does not raise his voice.

Róisín Ní Chonaill, Keel's co-founder and chief product officer, remembers that period differently. 'Cian saw the survey results and went into what I call his monastery mode,' she says. We are sitting in a café on Pearse Street, a ten-minute walk from the office. She stirs an oat milk flat white and does not glance at her phone once during the conversation, a detail I notice because she catches me noticing. 'He disappeared for a weekend and came back with a spreadsheet. Every hour of every person's week, colour-coded. It was beautiful and completely deranged.' She laughs, but the laugh carries an old argument inside it. 'I told him, you cannot design a company like a database schema. He said, why not?'

The spreadsheet became what Keel now calls its Operating Framework, a single Notion page that governs how fifty-two people spend their collective 2,080 working hours each week. The framework is not enforced by software. Nobody's calendar is policed. But the norms it sets have hardened into something close to ritual. Monday is for deep work: no Slack messages before 11 a.m., no meetings of any kind. Friday is for documentation, cleanup, and what Molloy calls 'thinking time.' The all-hands on Wednesday is the only mandatory synchronous gathering. Even the Thursday sprint demo is recorded and posted asynchronously for anyone who cannot attend. The framework has been edited seven times since January 2025, always after a company-wide vote.

'The question every small company faces,' Molloy tells me, back in the warehouse as the afternoon light goes grey through the skylight, 'is not whether to have meetings. It is whether the meetings you are holding are making decisions or just performing them.' The all-hands this morning covered four things: a customer churn risk, a hiring update, a demo of a new API endpoint, and a five-minute slot where a junior engineer presented a bug that had taken her three days to fix. That last item, Molloy says, is the one he cares about most. 'If you only hear from senior people in an all-hands, you are running a theatre. The junior engineer who stands up and says, I broke something and here is what I learned, that is the signal the company is actually alive.'

Asynchronous voice and video messages do more than just replace phone calls and meetings; they have multiple, compounding benefits for organizational productivity.Phil Kirschner, writing in <a href="https://www.forbes.com/sites/philkirschner/2024/11/26/9-ways-asynchronous-communication-can-improve-team-productivity/">Forbes</a>

Keel's async stack is unglamorous and meticulously maintained. Engineers record Loom videos for code reviews instead of scheduling live walkthroughs. The product team maintains a single Notion doc per feature, updated as the source of truth. Customer success uses Slack channels organised by account tier, with strict norms about response times but no expectation of immediate reply. Molloy points to the compounding effect: a question that would have been a thirty-minute meeting becomes a three-minute video watched at 1.5x speed by six people at different times. The math is straightforward but the discipline required is not.

On a Monday morning in early May, I visit the office unannounced. It is 10:30 a.m. and the main floor is silent. Twelve people are at their desks. Several wear noise-cancelling headphones. The Slack general channel is empty except for an automated message posted at 9 a.m. reminding everyone that deep-work hours extend until 11. At 10:58, a senior backend engineer named Darragh closes his laptop, walks to the kitchenette, and starts making a pour-over coffee. He does not speak to anyone. At 11:01, Slack begins to stir. 'You get used to it,' Darragh tells me later. 'The first month, it felt like working in a library where you were afraid to cough. Now, when I go to other companies' offices and see people interrupting each other all day, I feel claustrophobic.'

The Wednesday all-hands is the emotional centre of the week, and it is carefully staged. Molloy stands at the front of the room, but he does not present slides. The four bullet points on his A4 sheet correspond to four speakers, and each gets between five and twelve minutes. Ní Chonaill runs the demo slot. The customer churn update is delivered by the head of customer success, a woman named Aisling who joined from Intercom. Molloy sits in the front row when others present, legs crossed, hands still, watching. Afterwards, people linger. The forty-five-minute meeting spawns thirty minutes of unstructured conversation near the sofas. Molloy calls this 'the real meeting' and refuses to schedule it.

Not everyone has thrived inside the framework. Two engineers left Keel in 2025, and both, in separate exit interviews, cited the cadence as a factor. One told the HR manager that he missed 'the buzz of a chaotic Tuesday.' The other, a frontend developer who had been at the company for fourteen months, wrote in his departing email that the meeting-free Mondays made him feel 'isolated rather than focused.'

Emer Keating, Molloy's executive assistant and the person responsible for guarding the calendar, sees the tension from a different angle. Her desk is positioned between Molloy's office and the main floor, a placement she chose deliberately. 'I am the person people complain to before they complain to Cian,' she says. She has worked at three other Dublin startups, and she describes Keel's operating rhythm as 'the only one that has ever made me feel like my job was about protecting people's time rather than filling it.' She keeps a running tally of meeting requests that she has redirected to async formats. The number as of late April was 147. 'That is 147 hours of collective time,' she says. 'And I have only been here since September.'

The unspoken friction

There is something Keel's framework does not address, and it sits in the room like a third founder nobody mentions. The cadence works for engineers and product people. It works less well for the sales team, who live by a different clock entirely: the customer's. Sales at Keel operates what is effectively a parallel operating system. They hold their own standup on Monday morning, a pipeline review on Wednesday, and a close-out call on Friday afternoon. Ní Chonaill acknowledges the split. 'Sales is on a different cadence because sales is on the customer's cadence,' she says. 'We have not solved that. We have just agreed to live with two calendars.' The sales director, when I ask him about this, shrugs. 'I ignore the framework on Monday and Friday. Nobody complains. But I also know I am not really in the company on those days.'

The tension between engineering culture and go-to-market urgency is familiar to any startup crossing forty people, but the framework makes the split visible in a way that more chaotic companies absorb without noticing. A report published in April 2026 by the Forbes Business Council noted that small businesses are navigating the year with 'a blend of cautious optimism and uncertainty,' and that internal operating clarity was cited as a leading predictor of retention by 61 percent of surveyed firms. Keel has the clarity. What it may not have is a way to extend that clarity across functions that operate at different speeds.

On a Thursday evening in late April, I sit with Ní Chonaill in the empty office after the sprint demo has wrapped. The cleaners have not yet arrived. The Liffey is dark through the window. She is tired, and when she speaks, her voice is lower than it was in the café. 'The thing Cian and I argue about,' she says, 'is not whether the framework works. It works. The argument is whether it is making us faster or just making us feel less anxious.' She looks at the long oak table where the all-hands happens every Wednesday. 'Speed requires some chaos. We stripped out the chaos. I don't know yet if we also stripped out the speed.'

Molloy, when I put the same question to him the following morning, does not answer immediately. He is standing by the window, watching a rowing crew cut through the Liffey below. 'Róisín is right to ask it,' he says finally. 'But I think speed without chaos is the whole project. The question is whether it is possible.' He turns from the window. 'Ask me again in eighteen months.'