CONTACT
Bring a process, a deal or a bottleneck.
We start the conversation from something concrete, not from slides. The sooner you show a workflow, an investment decision or the place that is blocking growth, the sooner we can tell you whether there is something to work with — and what is worth doing as the first move.
BEFORE YOU WRITE
Four questions we start from.
You don’t need a brief — answers to four questions in an email or a note are enough. That is enough to make the first conversation about the work, not about introductions.
Which process is painful today, or what is blocking growth?
One workflow, one place in the organization, one symptom — that’s enough. The more concrete it is, the faster we can see whether AI is a real lever here.
Which decision do you need to make — and by when?
Investment, architectural, operational. Without a time horizon it’s hard to tell a strategy conversation from a pilot conversation.
Which data and systems are in play?
Briefly, without an audit — what you have (CRM, ERP, warehouse, documents, repositories), what is sensitive or regulated, what is missing. Mention the debt too — it saves both sides time.
What does success look like — what exactly do you want to see after deployment or after the decision?
A qualitative description is enough. Whether the process is faster and lighter, whether the decision is defensible to the board, whether the team stops re-keying data between systems — pick what genuinely changes the year.
WHO WE WORK FOR
Three entry points — pick your context.
Private Equity
AI/IT due diligence and value-creation maps across the portfolio — readable for the board and for the portfolio team.
Enterprise
Secure, governed agentic systems for complex organizations — with governance and auditability from day one.
SMEs and the mid-market
Practical automation pilots with the highest return — leverage without building your own AI department.
CHANNELS
Fastest — by email or on LinkedIn.
Two steady channels and one intention: we usually reply within one business day.
Email
Best with short answers to the four questions above — in the body of the email or in a one-page note.
LinkedIn
linkedin.com/in/adam-wszendybyl
Good for first setting the context, a short question or an introduction through a shared network.
We usually reply within one business day. That is an intention for how we work, not a contractual commitment — during periods of client work a reply can take longer. If the matter is urgent, say so plainly in the subject line.
Aurora Adam WszendybyłNIP PL 5732606147
Himalajska 17/2, 50-572 Wrocław
WHAT WE DON’T PROMISE
Three things you won’t hear in the first conversation.
The operator tone cuts both ways — we’d rather tell you what we won’t do than make a promise that can’t hold up under the other side’s due diligence.
We don’t promise magic numbers.
Without a process and without data, every metric is fiction. We show concrete results only once we have a process map, data sources and a clear success criterion — before that, we talk directionally.
We don’t price a deployment without a process.
Off-the-cuff quotes usually mean: more expensive, less, and slower. The quote comes after a short scoping — once we know what really needs to be done, who maintains the system after deployment and where our role ends.
We don’t start from a tool.
A model’s name, an agent framework or a specific cloud provider is not the starting point. The starting point is the work the team actually does, and the decision that has to be made. We fit the tool to that, not the other way round.
LET’S START
Write when you have something concrete.
A workflow, an investment decision or a bottleneck — with four answers in an email, that’s enough to make the first conversation about the work, not about introductions.