We sell engineering work with long delivery cycles to people who have usually been burned before. That makes this a consultative role rather than a volume one. You will spend more time understanding a problem than pitching against it.
What you will be doing
Finding and opening conversations with UK organisations that have a software problem worth solving.
Qualifying properly, including walking away. A badly matched project costs us more than an empty slot.
Running discovery alongside an engineer, so what we propose is something we can actually build.
Writing proposals that are specific about scope, assumptions and what is excluded.
Staying involved after signature. The handover to delivery is where most agencies lose trust.
What we are looking for
Around three years selling technology services business to business, ideally custom software or consultancy rather than licences.
Enough technical literacy to hold a credible conversation about systems, integrations and why a timeline is what it is. You do not need to code.
Comfort with long cycles and multiple stakeholders.
Willingness to tell a prospect something they do not want to hear, and to tell us when a deal is not real.
Clear, plain writing.
Nice to have
An existing network in insurance, manufacturing, logistics or the public sector.
Experience with tenders and procurement processes.
Familiarity with how AI projects are currently being bought, and how often they are oversold.
How we work
Targets exist and they are discussed openly. What we do not do is commit to delivery dates in a sales meeting without an engineer in the room. You will have that backing.
Applying
Send a CV and tell us about a deal you chose not to pursue, and why. That answer tells us more than a list of closed figures.