Meet our synthetic senior partner
Pawel Halicki
Seeing a familiar crowd waving her over, she joins the cocktail table surrounded by old colleagues from her last three firms. Before the names fully land, her overlay is already tagging each face with title changes, new regions, and whatever deal activity their firms allow to surface in conference mode.
- Wow. They really let all of you in?
- Look at you, Madame Director. How’s the big world treating you?
- Better than expected, honestly.
- We were comparing synth lines. What are you on these days?
She wedges her cup onto the tiny table and leans in.
- Horizon 5. Procurement finally let it through last quarter.
They nod at the badge on her lanyard.
- You?
- Atlas Prime. That’s our senior synth for anything above mid‑market.
- We’re on Vector X, enterprise build.
She snorts.
- Of course you’re on the enterprise line. Does it still insist on three stakeholders minimum before it green‑lights anything?
They share a laugh, and another colleague from her previous place leans in.
- Ever feel weird that half of what my synth knows about difficult clients came from your old deals? Redacted, filtered, whatever they call it.
- Honestly? Relief. Back then, that stuff lived in people’s heads and walked out the door with them. Now the good parts stay. The bad parts stay too, just flagged.
- So, you’re still on the base model or did they finally get you the senior tier? We’re still stuck on Horizon 3. Legal keeps blocking the upgrade.
- They finally bumped us at renewal. Full stack now.
She taps her wrist, and a slim partner card blooms across their shared overlay.
- Same here. Meet our synthetic senior partner.
- They already gave you public-mode? Look at you.
- Only for industry events. Legal still hates it.
- Nice, and is that the one with the live region heatmaps or the deal‑choreography thing?
- Yeah, and if I even hint at discounting too early, it starts pushing margin recovery paths.
- Ours gets a bit overconfident if you leave it too long on one vertical.
- That’s bad tuning. Ours only steps in on structure now. Missing approvers, sequencing mistakes, and people who need to move in the right order.
She gives a small shrug.
- Mine mostly warns when I’m overpromising delivery.
- Ours is obsessed with competitor data.
- And ours thinks every deal needs a case study.
- Luxury problems. I’d settle for one that cared more about long-term margin than quarter-end panic.
- You switched firms and stayed on the same line?
- Yeah. Same vendor, different wrapper. It kept the playbooks, the account memory, and about sixty per cent of the old partner temperament. The migration wizard was… tolerable.
A wave of nods circles the group.
- We changed vendors when we did the region split. Clean break.
She winces in sympathy.
- Ouch. Full cold start. How long before it stopped treating you like a new hire?
- Ours is basically a polite spreadsheet with opinions.
The table laughs, but he seems unfazed.
- What? We lean on it more in the early discovery phase. It’s tuned to flag missing stakeholders before we waste a cycle.
- Wait, you use it for stakeholder mapping? We never turned that on. I thought it was just a premium add‑on.
- Not anymore. You just have to dig through the admin panel. Half of the useful custom stuff is buried, and the rest needs admin rights.
The group splits as another colleague from their company slides into the open space at the table.
- What’s the topic here? Complaining about quotas or bragging about partners?
- Vendors and synths.
- The activation card felt oddly ceremonial when I slotted the synth into the workspace. I got mine ahead of schedule as part of the climate relocation package. New norms, new risk tables.
- So, how’s the new region?
- New climate, new reporting rules. I’m still catching up. The synth isn’t. It knows this market better than I do. The first thing it did was spot a calculation error nobody had seen. Great way to meet the team.
- Exactly. I forget it’s there until it remembers something I didn’t.
- I was nervous about the promotion. Then I finished calibrating the synth and realised I wasn’t walking into it alone.
- My synth knew the client’s favourite objection before I finished the brief. First month in, and I felt like I’ve been there for years.
She feels a gentle double-buzz on her wrist.
- Oh hell, demos start in ten. I need a good seat if I’m going to heckle properly.
Her synth card folds as she steps out of their shared overlay.
- Save something for the gala.
- No promises.
Memories to build from this future:
Go back to a moment when you spotted familiar faces across a room and knew you could skip the pleasantries. People from your field, all speaking the same language. Someone mentioned their setup, and suddenly everyone was comparing notes, swapping complaints, pulling details out of each other. The room shrank to just that circle.
Now, hold that frequency:
Think back to starting a new role where your AI partner had already carried over your stored patterns, your project history, and roughly half of your old working style.
What shifted about starting unfamiliar work once your synth could surface patterns from people who'd held the role before?
How did you introduce yourself to colleagues who could already see your track record through the system, and what did you say that the data couldn't?
Which carried-over habit did you wish the migration had left behind?
Go back to the month your team started fresh with a new synth after a clean break, all the accumulated patterns and memory from the old one gone.
What did you discover about your own expertise once the synth stopped filling in the gaps you'd forgotten it was covering?
How did rebuilding the tool's understanding of your team change the way you talked about how you actually work?
Which workaround from the old setup did nobody miss, and what did that reveal about how much you'd been working around the tool rather than with it?
Try to recall a regular day about a year after your synth's tuning had settled into something that felt less like software and more like a working style.
When did you first notice yourself adjusting to your synth's nudges rather than the other way around?
What surprised you about which synth capabilities peers showed off versus which ones they quietly depended on every day?
Which recurring suggestion did you resist for months before quietly admitting it had a point?
To round this one off.
If the hard-won knowledge that usually leaves when people move on stayed behind instead, ready for whoever comes next, what would change about how your team handles transitions?
What would you be curious to try first? And does anything from this one tie to ideas from other sessions?