Product engineering
From a business idea to a working product.
01 — Executive introduction
Welcome to SmartDevCo Global Sales
Your role is to create qualified business opportunities in markets where SmartDevCo can deliver real technology value.
Sales does not sell code.
Sales creates business opportunities.
SmartDevCo's technical team turns qualified opportunities into solutions, proposals, and delivered products.
Start the playbook- Market
- Target accounts
- Prospects
- Outreach, campaign, referral, or partnership
- Leads
- Qualification
- Discovery
- Qualified opportunity
- SmartDevCo discovery
- Proposal
- Negotiation
- Closed project
- Delivery
- Long-term account
- UnderstandFoundation
- FindAcquisition
- ConvertConversion
- OperateOperate
Your first 7 days
- Day 1Understand SmartDevCo
- Day 2Understand ICP and buyers
- Day 3Build your first target accounts
- Day 4Research decision makers
- Day 5Start outreach
- Day 6Follow up and qualify
- Day 7Review the pipeline with SmartDevCo
Before you contact anyone
02 — SmartDevCo
A technology partner for businesses building, modernizing, and scaling digital products.
SmartDevCo builds and delivers software. The sales message is the business outcome. Technology is how the work gets done, not the opening line.
Web and mobile
Applications people actually use.
Backend and APIs
The system behind the screens.
Enterprise systems
Software shaped around how a company operates.
System integration
Tools that need to share data.
Cloud and delivery
Architecture, release, and a team that can finish.
03 — The problem we solve
Sell the problem we can solve, not the technology we use.
04 — Target markets
Where to prospect.
These are markets to work. This page does not claim SmartDevCo has clients in every country listed.
Action
Choose the markets you will actually prospect.
Output
A short focus: region, country, and the kind of company you will look for there.
Next step
Match those companies to the ideal customer.
GCC
- Saudi Arabia
- UAE
- Qatar
- Kuwait
- Bahrain
- Oman
North America
- United States
- Canada
Europe
- United Kingdom
- EU markets
Australia
- Australia
- New Zealand
05 — Ideal customer
Companies that need software to move the business.
- Need software development
- Are building digital products
- Need system modernization
- Need integrations
- Need engineering capacity
- Need technical delivery support
- Are launching or scaling a digital product
StartupsScale-upsSMEsEnterprisesDigital businessesAgencies that need a delivery partner
06 — Buyer personas
The buyer depends on the problem.
Do not hunt one job title. Find the person who owns the pain.
Founder / CEO
Outcome, speed, cost, risk, execution.
CTO / CIO
Architecture, engineering capability, security, scale, integration.
COO
Operations, efficiency, automation, process.
Product leader
Delivery, roadmap, time to market, quality.
Procurement
Commercial process, compliance, vendor requirements, contracts.
07 — Lead generation
Six ways an opportunity enters the pipeline.
Action
Identify relevant companies from at least two acquisition channels.
Output
A researched target list: company, industry, country, website, buyer, problem hypothesis, and contact method.
Next step
Research the account before outreach.
LinkedIn, cold email, cold calling, account research, direct outreach.
Website, content, SEO, social, paid campaigns, lead forms.
Freelance platforms, RFPs, RFQs, government tenders, private tenders, procurement portals.
Digital agencies, marketing agencies, consultancies, technology companies, system integrators.
Existing relationships, clients, partners, professional network.
Conferences, meetups, industry communities, founder networks.
08 — Marketing to sales
Traffic is not a lead. A lead is not an opportunity.
- Audience
- Reach
- Engagement
- Lead
- Marketing qualified
- Sales qualified
- Opportunity
- Proposal
- Customer
ILLUSTRATIVE EXAMPLE
These figures are a teaching model. They are not SmartDevCo results.
- 1,000 reached
- 100 engaged
- 20 leads
- 8 qualified
- 3 opportunities
- 1 proposal
09 — What is a lead?
A person or company that might fit, or that showed interest.
- Submitted a form
- Replied to outreach
- Asked for information
- Asked for a proposal
- Answered an email
- Came through a partner
A lead is not automatically a sales opportunity.
10 — Qualified opportunity
Enough facts for SmartDevCo to take the next step.
A real problem.
Something to build, improve, integrate, or deliver.
SmartDevCo can potentially do the work.
A meaningful timeframe.
We know who is involved.
Budget or procurement, when it is known.
11 — Outreach
A channel, a message, and a next step.
Do not send identical generic messages. Every note needs a real reason.
Why are we contacting them?
Why is this company relevant?
Why could SmartDevCo help?
What is the low-friction next step?
When to use it
Named people at target accounts. First touch, or a follow-up after no email reply.
What to say
Hi [Name] — I work with SmartDevCo, a technology delivery partner. I noticed [company] is working on [area]. Are you running any digital product or systems work where an external team could help?
What not to say
A technology list, a price, or a generic "we do software."
Follow-up
One short note after a few days. Refer to the same business point, not a new pitch.
Next step
A 20-minute call to understand the problem. Not a proposal.
When to use it
A few days after the connection note, if there is no reply. One follow-up, tied to the same point.
What to say
Hi [Name] — following up on [area] at [company]. If a product, a modernization, or an integration is actually in motion, I can set a short call. If the timing is wrong, no need to reply.
What not to say
A second pitch. A technology list. Pressure.
Follow-up
Stop after this note unless they reply.
Next step
If they reply, move to discovery. If not, return the account to research.
When to use it
After you have researched the company. Best for a clear, forwardable note.
What to say
Subject: [Company] and a technology question Hi [Name], I work with SmartDevCo. We help companies build new products, modernize systems that no longer fit, and connect tools that do not share data. I looked at [a real signal: product, hiring, announcement]. Are you working on anything where an external technical team would be useful? If yes, I can learn the basics and introduce the right people. [Your name]
What not to say
Attachments full of stack diagrams. A quote. "Just checking in" with no context.
Follow-up
Two follow-ups, each adding one useful sentence. Then stop.
Next step
A discovery conversation, or a referral to the person who owns the problem.
When to use it
After the first email, once. Add one useful sentence. Do not restart the pitch.
What to say
Subject: Following up — [Company] Hi [Name], I wrote about [the real signal]. I will not send a generic pitch. If a technology initiative is real, tell me who owns it and we can keep the next step to one conversation. [Your name]
What not to say
"Just checking in" with no new context. A quote. A stack diagram.
Follow-up
This is the last note unless they reply.
Next step
A discovery conversation, or close the outreach on this account.
When to use it
Only when the channel is appropriate and you are allowed to message them there. A warm intro, or a market where WhatsApp is a normal business channel.
What to say
Hi [Name], this is [Your name] from SmartDevCo. We help companies build and modernize software. [Referrer / reason] suggested I ask whether you have a technology initiative an external team could support.
What not to say
A cold blast. Voice notes with a full pitch. Prices.
Follow-up
One follow-up. If there is no reply, move the account back to research or another channel.
Next step
Agree a time to talk. Capture what they said before you hand it over.
When to use it
When you know the company and the likely owner of the problem. Not as a script read to a switchboard.
What to say
Hi [Name], this is [Your name] with SmartDevCo. We help companies deliver digital products and modernize systems. I'll be brief: are you currently working on a product, a system replacement, or an integration where an outside team could help?
What not to say
A monologue. A technology tour. A request for budget in the first minute.
Follow-up
Send a two-line email the same day with what you heard.
Next step
Book discovery, or ask who else should be in the room.
When to use it
When someone who knows both sides has agreed you may use their name.
What to say
Hi [Name], [Referrer] suggested I reach out. I work with SmartDevCo. We help businesses turn a technology need into a working product. If something is in motion, I would like to understand it and introduce our team.
What not to say
Implying a closer relationship with the referrer than you have. A proposal before a conversation.
Follow-up
Tell the referrer you reached out. Do not pressure them to chase the lead for you.
Next step
A discovery call. Thank the referrer either way.
12 — Account research
Personalize the message around something real.
Do not send the same note to a list. Ten researched accounts beat a hundred generic ones.
Action
Research the account before you write.
Output
A completed target-account note you can copy.
Next step
Write one message from something real. This template is not stored.
TARGET ACCOUNT
Company:
Industry:
Country:
Website:
WHY THIS COMPANY?
Business signal:
Potential problem:
Why SmartDevCo?
BUYER
Name:
Role:
LinkedIn / Contact:
OPPORTUNITY HYPOTHESIS
Business problem:
Potential solution:
Current situation:
Existing system:
Expected scope:
Users / scale:
Integrations:
COMMERCIAL CONTEXT
Timeline:
Budget context:
Decision maker:
Procurement process:
NEXT ACTION:
- Company
- Website
- Industry
- Products
- Markets
- Growth
- Technology signals
- Recent announcements
- Hiring
- Current systems
- Likely pain
- Decision makers
13 — Discovery
Discovery before proposal.
You are collecting the picture. You are not designing the solution.
The outcome in business language.
The pain that makes this worth doing.
A system, spreadsheets, a vendor, or nothing.
A launch, a contract, cost, or risk.
Customers, staff, partners. Roles, not headcount guesses.
Name them. Do not evaluate them.
Payments, ERP, CRM, or "not sure yet" is a valid answer.
Record it. Do not accept it as a commitment.
A founder decision, a committee, or a tender.
Names and roles, if they will share them.
Ask once. Write "unknown" if they will not say.
Their words. This is what the proposal should answer.
14 — Qualification
Accurate information. Not a score.
Need+Fit+Timeline+Stakeholders+Commercial context=Qualified opportunity
If a piece is missing, say so in the handoff. Do not invent it to make the lead look stronger.
Qualification gate
No score. Missing information means not qualified yet. It does not mean a bad lead.
- Need?
- Business problem?
- Technology required?
- Relevant buyer?
- Timeline?
- Commercial context?
- Enough scope?
Not qualified yet
15 — Sales and SmartDevCo
Sales opens the door. SmartDevCo delivers the solution.
| Sales | SmartDevCo |
|---|---|
| Prospecting | Technical discovery |
| Outreach | Architecture |
| Relationship | Estimation |
| Initial discovery | Solution design |
| Qualification | Proposal |
| Opportunity information | Technical discussion |
| Follow-up | Delivery planning |
| Commercial coordination | Engineering |
| Account relationship | Project delivery |
16 — What sales must never promise
If you do not control it, do not commit to it.
- Final pricing
- Development hours
- Exact delivery dates
- Technical architecture
- A specific technology
- Guaranteed features
- Security or compliance certifications
- Performance guarantees
- Team size
The line to use: "Let me confirm that with our technical team."
17 — Opportunity handoff
Bring context, not just a name.
This opens WhatsApp with the brief for SmartDevCo. It is not stored on a server. Sales stays on the relationship. SmartDevCo owns the solution, the estimate, and delivery commitments.
- Sales
- Opportunity Handoff
- SmartDevCo technical discovery
- Solution
- Estimation
- Proposal
- Client discussion
- Negotiation
- Close
- Delivery
NEW OPPORTUNITY
Company:
Industry:
Country:
Contact:
Role:
Business problem:
What they need:
Current situation:
Existing system:
Users / scale:
Integrations:
Expected scope:
Web / Mobile / Backend / SaaS / etc.
Timeline:
Budget context:
Decision maker:
Procurement process:
Why SmartDevCo:
Client's next step:
Sales contact:
Submit opens WhatsApp +201024139097
Opportunity received.
Review happens from the WhatsApp brief. If WhatsApp did not open, use the button below.
Open WhatsApp18 — Sales pipeline
A process, not a tool.
There is no CRM behind this page. Use the stages so everyone means the same thing.
- 01Prospect
A company that fits. No conversation yet.
- 02Contacted
You sent a real, researched message.
- 03Responded
They replied. Interest is not yet scope.
- 04Discovery
You are learning the problem.
- 05Qualified
Need, fit, timeline, stakeholders, and commercial context are known or marked unknown.
- 06Technical discovery
SmartDevCo is in the conversation.
- 07Proposal
SmartDevCo has written the commercial and technical offer.
- 08Negotiation
Terms are being discussed. You coordinate. You do not reprice alone.
- 09Closed
Won or lost. Record why.
19 — Case studies
Two products you can talk about. Nothing invented.
Shuttlez
A transportation system with more than one app.
RiderCaptainBackendAdminRoutesBookingsPricingReal-time
Use it when the company needs transportation, mobility, booking, or a platform with more than one type of user.
- Transportation
- Mobility
- Booking
- Multi-sided platforms
- Real-time operations
ROOTACA
An education platform and the operations behind it.
StudentsProgramsAssessmentLearning pathsProgressAdministration
Use it when the company is in education, training, or learning and needs users, content, and progress in one place.
- Education
- Learning platforms
- Training
- Student management
- Assessment
- Progress tracking
20 — Objections
Concern, meaning, response, next step.
What it means
They think you want to replace the team.
Recommended response
That's fine. SmartDevCo can work beside a team when the need is capacity, architecture, or getting a project delivered.
Next step
Ask where the current team is blocked.
What it means
They want proof, or a way to end the call politely.
Recommended response
I'll send our site and one relevant example. What kind of project are you considering, so the example matches?
Next step
Send Shuttlez or ROOTACA only if the industry fits. Then ask for a time.
What it means
They need a sense of size.
Recommended response
Price follows scope, users, and integrations. I'll note what you're trying to do, and our technical team will estimate. I won't guess a number.
Next step
Capture scope. Hand off. Do not discount.
What it means
Budget pressure, or a comparison you have not seen.
Recommended response
I can't change a price that has not been scoped. If budget is the constraint, I'll record it so the team can say what a first version could include.
Next step
Write the budget range in the handoff. Do not promise a cheaper build.
What it means
A real date, or pressure.
Recommended response
I'll record the date and the scope. The technical team will say what can actually be delivered in that time.
Next step
Handoff marked urgent. No start date from you.
What it means
Timing. Not always a no.
Recommended response
Understood. What would need to be true before this is a project? I can come back then.
Next step
A dated follow-up. Leave the pipeline stage honest.
What it means
They have been burned, or a contract depends on a date.
Recommended response
I can't guarantee a date. I'll make sure our technical team sees the deadline and tells you what is realistic.
Next step
Technical discovery. You stay on the relationship.
21 — Operating rhythm
A cadence. Not a target you have to invent.
Daily
Prospecting, research, outreach, follow-ups.
Weekly
Pipeline review, qualification, opportunity review, follow-up review.
Monthly
Market review, channel review, campaign review, pipeline lessons.
No numeric targets are set on this page. Agree those with SmartDevCo separately.
22 — What to measure
Measure the pipeline. Do not invent the scoreboard.
Activity is not the same as performance. High outreach volume does not automatically mean high-quality sales work.
Activity
Prospects researched, outreach, follow-ups.
Engagement
Responses, conversations, meetings.
Qualification
Qualified leads, qualified opportunities.
Commercial
Proposals, pipeline value, closed projects. Value only after SmartDevCo has estimated.
23 — Mindset
SmartDevCo sales rules
- 01Target relevance over volume.
- 02Business problems over technology jargon.
- 03Research before outreach.
- 04Qualification before technical involvement.
- 05Never promise what you don't control.
- 06Bring context, not just a contact.
Don't chase everyone.
Target relevant companies.
Don't sell everything.
Sell the problem we can solve.
Don't promise what you don't control.
Bring the technical team in.
Don't stop after the first message.
Follow up professionally.
Don't bring only a contact.
Bring context.
24 — Your mission
Build the pipeline.
Not random leads. A sequence you can repeat.
- Target
- Research
- Connect
- Discover
- Qualify
- Handoff
- Proposal
- Project
- Relationship
Find the right problems.
Build the right relationships.
Bring the right opportunities.
SmartDevCo builds the technology.
Review the playbook again