Everyone pitches. I bring it already built.
I'm Abdul Moeed, Business Development Manager at Innovatek Global, where I lead Forge, our B2B sales team. I open cold markets on Upwork and outbound, scope the build with engineering before the call, and turn “let me think about it” into signed contracts.
What I sell, scope and close
Abdul Moeed.
I sell things that have to actually get built.
There is an easy version of this job. Send two hundred proposals, promise whatever the client asks for, hand it to engineering, and let delivery figure out the rest. It works for about one quarter.
I do the harder version. Before I pitch anything, engineering has looked at it, and usually we have already built a piece of it. So when I say we can do it, that is not a sales claim. It is a thing on a screen.
That is the whole difference. It is slower per deal, and it wins the deals that matter.
Build first. Then sell.
I'm Business Development Manager at Innovatek Global, a UK technology group building AI systems, games, web platforms and custom software, with its delivery hub in Multan. I joined in February 2025 and now lead Forge, our B2B sales team.
Alongside that I'm finishing a BSCS at MNS University, which is less of a footnote than it sounds. Being able to read a spec, question an estimate, and tell a client honestly what is hard about their idea is most of why deals close.
Day to day, that means:
- Winning work on Upwork against forty other applicants, on positioning rather than price
- Running trigger-based outbound where the work goes out before the meeting is requested
- Turning vague, large, technically complex asks into scopes engineering can price
- Building the Forge team into a system rather than a group of people making calls
Six jobs. One outcome: signed work.
From the first cold touch to the signature and the handover. Pick the part you need, or the whole pipeline.
Upwork & Marketplace BD
Profile positioning, disciplined job screening, and proposals written for a buyer reading on a phone between meetings.
See the playsOutbound B2B
Trigger-based lists, build-first cold email that sends work instead of asking for time, and LinkedIn that does not read like automation.
See the playsDiscovery & Technical Scoping
Turning a vague, ambitious ask into a written scope engineering can price and the client recognises as their own idea.
See the playsProposals, Pricing & Closing
Documents that argue for the price and survive the meeting you are not in. Three-option pricing, objections answered in advance.
See the playsSales Team & Pipeline Ops
Building Forge into a system: one written playbook, evidence-based pipeline stages, reviewed calls, and a documented 30-day ramp.
See the playsComplex & Large Builds
Multi-month, multi-team engagements where the scope is genuinely hard: AI products, game builds, platforms with real integration risk.
Let's talkEvery play I run, written down.
This is the actual system, not a list of adjectives. Filter by the part of the pipeline you care about, open any card to see how it runs step by step, and use the copy-link button to send someone just one section.
Named wins, with the detail.
Real engagements: what came in, how it was scoped, and what got signed.
Anatomy of a build-first win.
The play everything else is named after, broken down move by move.
Rather than describe it, we built the one screen you'd look at every morning.
A working slice, in their branding, on the call. Not a deck about what we could do. The thing, on screen, being clicked.
Why a prototype beats three meetings of reassurance
1 · Pick the slice
Not the architecture, not the roadmap. The single screen or workflow the client would touch every day. It carries the highest emotional signal at the lowest build cost, which is exactly the ratio a sales asset needs.
2 · Build it in hours
Engineering treats it as a sales asset, not a deliverable. Rough is fine. Their branding and their data being in it matters far more than the quality of the code behind it.
3 · Demo it live
This is the moment the conversation stops being about whether we can, and starts being about when and how much. Nobody asks for references after they have watched the thing work.
4 · Let their reaction write the scope
What they ask for immediately after seeing it is the real requirement list. It is more honest than any structured discovery call, because they are reacting to something real instead of imagining it.
From cold contact to signed scope.
Qualify hard
Budget signal, decision maker, and a definition of finished. If those three are not there, I say so early rather than expensively later.
Build the proof
A teardown, a mockup, or a working slice, made specifically for them. The work goes out before the meeting is ever requested.
Scope with engineering
Every integration, data source and dependency named. The number never leaves the building without a sanity pass from the people who will build it.
Close and hand over
Three options rather than one number, objections answered in the document, then a handover where delivery inherits context, not surprises.
What the record actually says.
No invented numbers and no borrowed logos. This is what is verifiable.
The deal is won before the call. Everything after is paperwork.The only rule I sell by
Tell me what you're trying to build.
Bring the messy version. The half-formed idea, the project that stalled, the thing three agencies said yes to and none of them shipped. I'll tell you honestly what is hard about it, and what it would actually take.
Currently taking on new B2B and product engagements.