App Growth Summit London 2026 runs Thursday, September 3 at Tower Hotel. Thirty speakers, 12+ sessions, 300+ app growth people in one building. If your ICP includes mobile-first SaaS, marketplaces, or consumer apps, this is one of the few London conferences where the room is dense with buyers rather than vendors.
Here's how we'd work it.
The speaker list is your prospect list
Supercell, Vinted, Just Eat Takeaway, Snap. Those four names alone tell you the room skews toward companies with real mobile growth budgets and real outbound problems. Growth leaders at that scale don't take cold emails from strangers. They do take a 10-minute conversation at a conference if you've done your homework.
Pull the speaker list the week it goes live. For each name, find the one thing they've shipped or said publicly in the last six months. That's your opener. Not "I loved your talk" (you haven't heard it yet). Something like "You moved Vinted's onboarding to a two-step flow last quarter, we saw the retention lift in the app store reviews." That's a conversation. The rest is noise.
The discipline is in the sequencing. Build the list into your CRM as a named segment before the agenda drops, not after, so each contact carries an owner, a source note and a next-step date. Work it in three passes: first, the ten speakers whose remit overlaps your ICP most directly; second, the adjacent roles — lifecycle, monetisation, CRM — where a growth budget often sits one layer down from the headline title; third, the long tail, which you touch only if the first two passes leave capacity. Thirty speakers is not thirty emails. It is perhaps eight conversations worth having, and the value comes from knowing which eight before you arrive.
Timing matters as much as targeting. A note sent the week the list publishes lands while the speaker is still thinking about their session and before their inbox fills with conference noise. A note sent the day before the event competes with everyone else doing the same thing badly. Book the ten minutes then, and confirm it forty-eight hours out with a single line referencing the session topic — not a re-pitch.
We've written before about how to work a founder-heavy conference without wasting two days. The same rules apply here, just with a narrower ICP.
300 attendees is small enough to actually meet people
Most London conferences are 2,000+ people and you leave with a bag of lanyards and no pipeline. 300 is different. You can have 15 real conversations in a day if you're deliberate about it. That's roughly one every 30 minutes across an eight-hour event, which is achievable if you skip the panels that don't map to your ICP.
Our rule: two sessions in the morning, two in the afternoon, the rest of the time on the floor. Sessions are for context. The floor is for pipeline. The math only works if you treat the schedule as a constraint rather than a menu. With 30 speakers across a single day, the programme will almost certainly run on parallel tracks, which means every slot you spend in a room is a slot you're not spending in the room where your buyers are standing. Before you go, pull the speaker list and mark which sessions touch your ICP's actual problems — onboarding friction, retention, paid acquisition economics — and treat everything else as optional. Two morning, two afternoon is generous; one strong session per half-day is often enough.
The floor time needs structure too. Fifteen conversations doesn't happen by accident. Book three or four meetings in advance through the event app or LinkedIn, and leave the rest open for serendipity. Arrive with a specific question rather than a pitch — founders at this scale respond to "how are you handling X" far better than a demo request. And follow up within 48 hours, while the context is still fresh; a conference conversation that goes cold over a week is a conversation you paid for and didn't collect.
If you're a solo founder or a two-person sales team, this is the right size of event. Big enough that your buyers show up. Small enough that you're not competing with 40 other vendors for the same five conversations. At a 2,000-person show, the vendor-to-buyer ratio quietly works against you — sponsorship tiers buy visibility you can't match, and the people worth meeting are already booked. At 300, the ratio is closer to something a small team can actually work. That's the whole argument for attending events of this size: not that they're cheaper or more convenient, but that the density of relevant conversations per hour is high enough to justify the day out of the business.
What to actually bring
Not a booth. Not a stack of one-pagers. Bring:
- A one-line description of what you do that a growth lead would repeat to their boss. If it takes more than 12 words, cut it. Test it out loud before you travel: if you stumble, they will too, and the version that reaches their VP will be even less accurate than the one you gave.
- Three specific questions you want answered about how their team runs outbound or lifecycle. Real questions, not discovery-call theatre. "Who owns the sequence when a rep goes on leave?" tells you more about their operation than any pitch deck will, and it signals you have actually thought about their workflow rather than your quota.
- A follow-up mechanism that isn't "let me send you a deck." A calendar link with two slots the following week is better than a promise. Better still is a note you write on the spot, in front of them, so the context is captured while it is fresh and the follow-up references the actual conversation rather than a generic template.
The mistake we see most often: founders treat conferences as a lead-gen channel and forget that the actual output is a warm intro to a follow-up call. The conference is the top of the funnel. The work happens after. With 30 speakers across a single day at the Tower Hotel, the schedule will compress conversations into short windows, which makes preparation the variable you control. Decide in advance which sessions map to your three questions, and treat the gaps between them as the real working hours. A founder who leaves with six genuine follow-ups and no badge scans has done better than one who leaves with sixty contacts and nothing to say to any of them.
Follow-up is where most of the pipeline dies
You'll meet 15 people. Twelve will say "great to meet you, send me something." Nine of those will ignore your email. Three will reply. One will book. That's a normal conversion rate for a conference, and it's fine, as long as you actually send the follow-up within 48 hours and personalise it to the conversation you had.
This is where most teams fall down. They come back to a full inbox, the conference follow-ups get deprioritised, and by the following Wednesday the conversation is cold. The failure is rarely one of intent — everyone means to follow up — it's one of sequencing. The follow-up competes with the backlog that accumulated while you were at the Tower Hotel, and the backlog always wins because it has deadlines attached and the conference contacts don't. By the time you get to them, you're reconstructing a conversation from a badge scan and a half-remembered anecdote, which is exactly the condition under which generic outreach gets sent.
The fix is procedural, not motivational. Before September 3, decide what "personalised" will mean in practice: one specific detail from the conversation, one reference to something they said about their stack or their team, and a concrete next step rather than "let's stay in touch." Write the template skeleton in advance so the only variable is the detail itself. We've written about which deliverability tools actually survive a real outbound stack, and the short version is: the tooling matters less than the discipline of sending the follow-up while the memory is fresh. A sequencer will queue the email; it won't remember what they told you about their migration timeline.
If you're running a small team, block the morning of September 4 for follow-ups before you book anything else. Treat it as a calendar commitment with the same weight as the event itself, and resist the urge to schedule it for "later in the week" — the 48-hour window is doing real work, because it's the difference between a message that reads as a continuation of a conversation and one that reads as a cold approach with a name attached. That's the highest-ROI hour of the whole event.
Is it worth the day?
Depends on your ICP. If you sell to mobile-first consumer apps, marketplaces, or gaming companies, yes. The speaker roster is unusually strong for a 300-person event and the attendee list will reflect it. If your buyers are enterprise IT or UK public sector, skip it. The room won't be there.
For everyone else, the calculation is less about the ticket and more about what a single day off the pipeline actually costs you. At 300 attendees, this is a room you can work end to end rather than a conference where you spend half the day queueing for coffee. That density matters for a founder or solo operator: thirty speakers across one track means the agenda itself functions as a filter, since anyone paying to be there has already self-selected into the mobile growth ecosystem. Your qualification burden drops before you've said a word.
The prep is where most people lose the day. Concretely:
- Before: pull the speaker and sponsor lists, identify the ten accounts worth a conversation, and have a specific reason to talk to each. Generic "what brings you here" openers waste the density advantage.
- During: work the floor between sessions rather than defaulting to the keynote room. The hallway is where the buyer conversations happen.
- After: send follow-ups within 48 hours with something referenced from the conversation. A day of conversations decays into nothing without this step.
That's the whole playbook. There's no clever version. The event rewards operators who treat it as a focused sales day rather than a learning day, and punishes those who book it, attend passively, and wonder why the pipeline didn't move.
What we'd do next
If you're going, pull the speaker list this week and build a shortlist of 10 people you actually want to meet. Treat that shortlist as a working document rather than a wish list: for each name, note the one question you'd ask, the specific thing your product or service does that maps to their stated remit, and the reason a conversation would be useful to them rather than just to you. That last column is the one most people skip, and it's the one that determines whether a follow-up gets a reply. Rank the ten by relevance, then decide which five you'd approach first if the day gets away from you — because it will.
From there, work backwards from September 3. Personalised openers and meeting briefs are only useful if they exist before the event, not after it, so the practical sequence is: shortlist this week, research and draft openers the week after, then send in the window where a message is timely but not forgotten. Keep each opener short and specific — a reference to something the person has actually said or shipped, plus a single clear reason to talk. Avoid the generic "are you attending?" template; it reads as volume outreach and gets treated accordingly.
If you want help turning that list into personalised openers and meeting briefs before September 3, give MiraReach a try. It drafts the email, you press send.
— Mira