Questions you'll probably ask before booking.
The front page sells the offer. This page answers everything else: how engagements are structured, what gets delivered week by week, who owns what, what hours work, and what disqualifies a company from working with me.
How long, what shape, what happens at each milestone.
How long is a typical engagement?
Six months. The structure is three plus three: the first three months I do the work and assess where your presales workflow needs improvement. Months four through six I build the systems that fill those gaps, based on what we learned in the first half. After six months, the engagement either ends with a clean handoff or continues month to month for as long as the work justifies it.
Why three plus three and not just six months flat?
Because the value of the second three months depends on what we learn in the first three. The first three are about doing the work and understanding how it actually flows through your function. The second three are about building the highest-leverage systems based on what we observed. If we tried to plan six months of builds upfront, we'd build the wrong things.
Can I cancel after three months if it isn't working?
The minimum commitment is three months, and at the end of that period you have a clean exit with everything we built up to that point. Most engagements continue into months four through six because the agentic work compounds the value of the first three months considerably, but the structure protects you from being locked into something that isn't landing.
Do you offer a paid pilot or trial?
No. The first three months of any engagement function as the structured introduction: by the end of week two you have a written diagnostic of what I'd build and why, and by the end of week six you have the first concrete deliverables in your team's hands. If after the first three months it isn't working, the engagement ends and you keep everything we built.
Can the engagement run longer than six months?
Yes. After the initial six months, engagements continue month to month for as long as there's work that justifies it. Some engagements wrap cleanly at month six because the function is in good shape and the agents are in production. Others continue indefinitely because new agent opportunities surface as the company grows.
In customer conversations, not just behind them.
Do you actually run sales calls or just advise?
I run them. In Foundation, I am your senior SE in European hours: discovery calls, demo delivery, POC scoping, technical close. In Lift, I shadow your existing team and step in as primary SE when you need coverage for sick leave, holiday, or new hire ramp. Either way, I'm in the customer conversations, not just behind them.
Do you cover the full sales cycle or just technical stages?
Technical stages by default: discovery, demo, POC, technical close, and handoff to customer success. I can support qualification calls and commercial negotiations when needed, but the core of what you're hiring is the technical end of the funnel where most enterprise deals get won or lost.
Are you on call for ad hoc demo support, or is this scheduled work?
Both. Scheduled work is the bulk of the engagement: planned demos, discovery calls on the calendar, POC milestones, weekly enablement work. Ad hoc support happens when a deal cycle moves faster than the calendar and you need an SE in a meeting tomorrow. I keep slack in my schedule for it.
Concrete artifacts, with examples.
What does the first deliverable of any engagement look like?
A written diagnostic, three to five pages, delivered at the end of week two. For Foundation, it covers what your demo and deck need to land your actual ICP, where the technical close is leaking deals, and which workflows are generating the most busy work for your team. For Lift, it names the two or three highest-leverage processes where your SEs are spending time that should be automated, sized in hours per SE per week. Both versions end with a recommendation on what to fix first and how it fits into your existing tools.
What does an enterprise readiness diagnostic actually contain?
A written evaluation of what your product needs to win enterprise deals. Specific integrations the buyer's stack expects (named, with priority). Authentication and authorisation requirements (SSO providers, SCIM, role-based access). Certifications you'll be asked for (SOC 2 type, ISO 27001, regional equivalents). Multi-tenancy and workspace structure (where your current model breaks down at scale). The output is a prioritised product todo list your engineering team can act on directly, not a strategy deck.
What does an agentic meeting prep brief actually look like?
For each call on your calendar, a brief assembled by the discovery agent and delivered to your inbox before the meeting. Company background and recent news. Stack and likely integration surface. ICP fit assessment with confidence. Likely technical objections based on what similar customers have raised. Suggested demo path and which features to lead with. Key people on the call with public-facing background. The brief is editable, not a black box, and your SE can override anything before the call.
What does the security questionnaire and RFP automation produce?
A response system grounded in your own product documentation, security posture, and past completed questionnaires. When a new questionnaire arrives, the system drafts answers with citations back to the source material. Your SE reviews, edits, and approves before sending. A questionnaire that previously took a week of SE time turns into a half day of review.
What does the verified-knowledge SE answer bot do?
A knowledge layer grounded in your product, your past deals, your security posture, and your documented sales positioning. AEs ask it product questions. SEs ask it precedent questions ('how did we handle this objection at that other deal'). CS asks it onboarding questions. Answers come with citations. It lives wherever your team already works, and it compounds with every deal because every closed-won and closed-lost feeds back into it.
Do you do bespoke per-customer technical work?
Yes, when the engagement calls for it. Examples include competitor migration scripts (when the buyer is switching from a specific incumbent), data quality evaluation harnesses (when the buyer needs to prove their data is clean enough for your product), and technical suitability evaluators that score whether a prospect is actually a fit before the SE invests deal cycles. These are hand-rolled per engagement because the shape of the work depends on your specific stack and buyer.
What else do you build beyond what's on the front page?
It depends on what the diagnostic surfaces. Past examples include turning sales calls into reusable reference assets, mapping sales motions against where enterprise deals actually break, building per-customer fit scoring so SEs don't waste time on bad deals, and connecting lead generation into the wider GTM motion. The starting point is always what's generating busy work for your team right now, not a fixed list.
No licensing. No lock-in. You keep everything.
Who owns the agents you build during the engagement?
You do. Source code, prompts, configuration, vector indexes, and operational runbooks all transfer to your team at the end of the engagement. You can keep operating them, you can modify them, you can throw them away. There is no licensing, no usage fees, no lock-in to any platform I run.
What if I want you to keep operating the agents after the engagement?
That's available as a separate ongoing operator engagement. Some companies want to own the code but not the operational burden of running it, and prefer to keep me on a smaller monthly engagement that handles monitoring, updates, and incident response. We can structure that at month six if it makes sense.
Do you sign NDAs?
Yes, mutual NDA before any technical detail of your product or sales motion changes hands.
European hours, US East Coast overlap.
What hours do you actually work?
European business hours from a base in Spain (CET). I overlap fully with European customers and prospects. For US customers, I overlap reliably with US East Coast morning hours, and I keep flexibility for pre-agreed US East Coast afternoon coverage on specific dates when a deal cycle requires it.
How many hours per week do you commit to a single engagement?
It depends on the engagement shape and what we're building at that point. Foundation engagements are typically the heavier human-hours commitment because I'm acting as the SE in customer calls. Lift engagements are typically lighter on direct hours and heavier on systems work that compounds beyond the time I put in.
Are engagements exclusive, or do you take other clients in parallel?
Engagements are not exclusive. I take a small number of concurrent clients deliberately, so each engagement gets real attention and so what I learn building systems for one customer makes me better at the next. If you need exclusive coverage, that changes the engagement shape and we should discuss it specifically on the call.
What happens if you're sick or on holiday during an engagement?
Planned holidays are agreed in advance and worked into the engagement schedule. Unplanned absences are rare but happen. For Foundation engagements, I have a small backup network of senior SEs for emergency coverage. For Lift engagements, your existing team is the natural backup since the whole point of the offer is to support them, not replace them.
Who this is right for, and who it isn't.
Who is Foundation right for?
Two situations. First: B2B tech companies, typically seed to series A, where the founder is still running every demo and you're hitting the point where founder-led presales doesn't scale. Second: companies of any stage that already have a US presales function but just hired a European AE who has no in-timezone SE support and is trying to close enterprise deals alone.
Who is Lift right for?
B2B tech companies with an existing SE team, typically series A through series C, where the team is hitting capacity walls and the answer can't be more headcount. Lift also works for legacy enterprise software companies where the SE function is mature but the agent transition hasn't started yet.
What if I'm not sure which engagement is right?
Book a discussion. The first ten minutes of the call usually surface enough about your situation to know which engagement fits. If neither does, I'll say so on the call and we save each other the rest of the conversation.
Do you only work with US-headquartered companies?
No. I work with B2B tech companies based anywhere, with the natural fit being companies that have European customers or European go-to-market ambitions where in-region SE coverage matters.
What disqualifies a company from working with you?
Three things. First, if you're not selling B2B technical products to other businesses, what I build won't apply cleanly. Second, if you're looking for someone to do hourly contract work without engagement structure, this isn't the right shape. Third, if you don't want systems built and you just want a contract SE for deal coverage, the value of the engagement collapses to ordinary fractional hours and you're better served by someone cheaper.
Clean handoff. Open door.
What does the handoff look like at month six?
A documented walkthrough of every agent in production, the operational runbook for each, the source code in your repository, the credentials handed over to your team, and a written summary of what was built and why. If you want training sessions for whoever on your team is going to inherit the work, those are included.
Can I rehire you for another engagement later?
Yes. Some companies engage Compound/SE in stages: a Foundation engagement at series A, then a Lift engagement two years later when the team has grown. The second engagement is faster because I already know your stack, your buyer, and your sales motion.