
3-Month Business Development Program · OBDP
Month 1 — Business Discovery, Development & System Planning
Focus: Deciding what the business actually builds, how its systems talk to each other, what data it collects and measures, where customers will come from — and then assembling every decision of Month 1 into one Online Business Master Blueprint.
The business now has a legal identity, a bank account, payment gateways, a provider shortlist and named owners for the work. What it does not yet have is a decision about what actually gets built.
This is the section where founders lose the most money. They build a mobile app when a landing page would have sold, or they buy an expensive platform for a business that has not made its first naira. The technology is not the business — it is the machinery the business runs on, and machinery should be sized to the work.
We will go through every layer from the landing page up to the admin dashboard, in plain language, so that by the end you can say with confidence what your business needs now, what it needs later, and what it does not need at all.
A landing page does one job: it presents an offer and captures an action — a purchase, a booking, a phone number, an email. One page, one message, one action. It is the fastest thing you can put online that makes money, and for most businesses it should come first.
A website is several pages that explain who you are, what you sell, where you are and how to reach you. It builds trust and answers the questions a buyer asks before they commit.
A web application is different in kind: customers log in, data is stored against their account, and they come back to use it. That is a product, not a brochure — and it demands a database, authentication and real ongoing maintenance.
A native mobile app lives in the app stores and can use the phone's camera, notifications and offline storage. It is expensive to build and to maintain, because you support two platforms and every update must be reviewed and released.
A progressive web app — a PWA — is a website that behaves like an app: it installs to the home screen, works offline and sends notifications, without the app store. For most small businesses it delivers most of the benefit at a fraction of the cost, and it is the sensible first step before a native app.
An e-commerce system is the whole selling machine: product catalogue, cart, checkout, payments, orders and delivery. If you are selling standard products, an existing platform will get you live in days. If your product is unusual, or the store must connect to your own systems, a custom build earns its cost.
The frontend is everything the customer sees and touches. The backend is the part they never see: the logic that decides what happens when they click, and the rules that keep one customer's data away from another's.
The database is where the business's records live — customers, orders, products, messages. Design it around the questions you will need to ask of your data later, not just the screen you are building today.
Authentication is how the system knows who someone is: login, passwords, one-time codes, and permissions that decide what each person may see. Getting this right early is far cheaper than adding it later.
Work in this order: a landing page that takes payments and captures leads, then a website that builds trust, then a web app if customers need accounts, and a mobile app only once your customers are actually asking for one.
Every layer you add costs money monthly and demands attention. Build the smallest thing that lets the business sell, launch it, and let real customer behaviour tell you what is missing — that is far cheaper than guessing.
Landing Page
One page, one offer, one action. The fastest thing online that makes money.
Website
Several pages that explain the business and build trust before a buyer commits.
Web Application
A product customers log into — needs a database, authentication and maintenance.
E-commerce System
Catalogue, cart, checkout, orders and delivery — platform or custom.
Mobile App
Native app-store presence. Expensive to build and maintain — earn it first.
PWA
A website that installs to the home screen, works offline and sends notifications.
Frontend
Everything the customer sees and touches.
Backend
The logic and rules behind the scenes that the customer never sees.
Database
Where customers, orders, products and messages are stored.
Authentication
How the system knows who someone is, and what they are allowed to see.
CMS
A system that lets you update content without touching code.
Customer Portal
A logged-in area where customers manage their own account and orders.
Admin Dashboard
Your side of the system — orders, customers and reports in one place.
Every tool you chose in the last session has a door on it. An API is that door — the documented way one system asks another to do something. Understanding APIs is what separates a business that runs on connected systems from one where a person copies data between dashboards all day.
You do not need to write code to understand this. You need to know what an API can do for you, what it costs, and what to demand of the person who builds with it.
Then we look at AI — not as a novelty, but as a specific set of jobs inside the business where it genuinely saves time or earns money, and where it does not.
An API is a contract: you send a structured request to a service, and it sends back a structured answer. Your website asks the payment gateway to create a checkout; the gateway replies with a link. No human is involved, and it happens in a second.
This is how your tools become one system instead of many. When your form submission creates a contact in your CRM, sends a welcome email and starts a WhatsApp sequence — that is APIs doing the work.
When you evaluate any provider, ask whether it has a documented API. A service with no API cannot be automated, and you will be doing its work by hand forever.
An API key is the credential that proves a request came from your system. It is a secret: it lives in secure storage, never in code that ships to a browser, and it is rotated if it ever leaks.
Most modern services are REST APIs — a set of clearly named endpoints you call to read or change data. Good documentation, with examples you can copy, is worth more than a clever feature list.
A webhook is the reverse direction: instead of your system asking, the service notifies you the moment something happens. A successful payment, a new message, a completed form. Delivery, access and notifications should all be triggered by webhooks — not by a customer's screenshot or a person checking a dashboard.
AI earns its place in four places: answering the questions customers ask over and over, qualifying and routing leads so your time goes to the serious ones, generating and adapting content at a volume a person cannot match, and reading large amounts of data to surface what is worth noticing.
It does not belong where a wrong answer is expensive and unverifiable, where the task is already solved by a simple rule, or where you have not yet decided what good looks like. Automating a process you have not defined just produces mistakes faster.
Budget for it like any other provider: AI usage is a recurring operating cost that grows with your customers, so it belongs in the cost sheet you will build at the end of this session.
API
The documented way one system asks another to do something.
API Key
The secret credential that proves a request came from your system.
REST API
A set of clearly named endpoints for reading and changing data.
Webhook
The reverse direction — the service notifies your system the moment something happens.
Email / SMS / WhatsApp API
Transactional messages sent by your system, not by hand.
CRM API
Creating contacts, logging activity and moving deals without a person typing.
AI API
Models called from your product for support, sales, content or analysis.
Database Integration
Keeping your systems reading from and writing to one source of truth.
OAuth
Letting a customer connect an account safely, without sharing a password.
Real-world examples:
Everything your business does produces data: who visited, what they clicked, what they bought, what they abandoned, what they came back for. Left alone, it is noise. Measured properly, it is the only honest advisor you will ever have.
The mistake is collecting everything and reading nothing. Today we decide what is worth recording, which numbers actually change decisions, and how to see them without opening five dashboards.
Customer data is the record of who buys from you and how to reach them — your most valuable asset and the one most easily lost by renting a platform that will not let you export it.
Product, sales, marketing and financial data describe what you sell, what it earns, what it cost to earn, and where the money actually went. Website and user-behaviour data describe the path from stranger to customer, and exactly where that path breaks.
Collect deliberately. Every field you store is a responsibility — you must keep it safe, keep it accurate, and be able to delete it when a customer asks. Store what you will use.
Track events, not just visits. A page view tells you someone arrived; an event tells you they started checkout, failed a payment, or abandoned a cart — the information you can act on.
Funnels turn those events into a picture: how many people moved from one step to the next, and where the drop-off is largest. That single view usually tells you what to fix next.
Retention matters more than traffic. A small audience that returns and buys again is worth more than a large one that never comes back — so measure whether people return, not only whether they arrived.
On the marketing side: reach and impressions tell you how many saw you; click-through rate tells you whether the message worked; cost per lead and customer acquisition cost tell you what a customer costs you to win; ROAS tells you whether the spend returned more than it consumed.
On the sales side: leads and qualified leads tell you how much real opportunity exists; conversion rate tells you how well you close; average order value, repeat purchases and customer lifetime value tell you what a customer is worth over time.
The comparison that matters most is customer acquisition cost against customer lifetime value. If it costs more to win a customer than that customer will ever pay you, no amount of traffic will save the business — and you will see it here first.
Pick a handful of numbers — the ones that would change what you do this week — and put them on one screen you look at on a schedule. Everything else is available when a question arises.
Set up the tracking before you need it. A pixel or an event added after a campaign has run cannot tell you anything about that campaign, and the traffic you already paid for is gone.
Customer Data
Who buys from you and how to reach them — your most valuable, most portable asset.
Sales Data
What sells, at what price, to whom and how often.
Financial Data
Where the money came from and exactly where it went.
Website Analytics
Traffic, sources and pages — where people come from and where they stop.
Event Tracking
Recording actions, not just visits — the information you can act on.
Funnel
Step-by-step conversion, and the exact point where people drop off.
Conversion Rate
The share of visitors who take the action you want.
Retention
Whether customers come back — worth more than raw traffic.
Customer Acquisition Cost
What it costs to win one customer.
Customer Lifetime Value
What one customer is worth over the whole relationship.
ROAS
Whether your ad spend returned more than it consumed.
Dashboard
The few numbers that change your decisions, on one screen.
Pixel
Tracking installed before a campaign runs — useless if added afterwards.
Real-world examples:
A finished product with no customers is a hobby. Today we answer the question that decides whether the business lives: where will these customers actually come from?
There are only a few families of channels — organic, paid, partnership and direct — and every platform you have heard of belongs to one of them. Understanding the family tells you what the channel will demand of you, long before you spend money on it.
The goal is not to be everywhere. It is to choose two or three channels you can genuinely commit to, and to run them properly.
Organic means you are not paying per view: social media, search, blogging, video, email to a list you own, communities, referrals and word of mouth. The currency here is consistency and time, not budget.
Search engine optimisation is the highest-value organic channel for most businesses, because it answers people who are already looking for what you sell. It is slow to compound and, once it does, it keeps working without further spend.
Email and WhatsApp are the only channels where you own the audience rather than renting it from a platform. Build the list from day one — a social following can be taken away by an algorithm change; your list cannot.
Paid means you pay for reach: Meta Ads, Google Ads, YouTube, TikTok, LinkedIn, display and search advertising. The advantage is speed and control — you decide who sees the message and you can measure the result precisely.
The risk is that it flatters you. Spend always produces impressions; it does not always produce profit. Judge paid channels by customer acquisition cost against customer lifetime value, never by how busy the ads looked.
Retargeting is the most efficient paid channel most businesses underuse: showing your offer again to people who already visited, watched or started a checkout. They know you already — you are not introducing, you are reminding.
Partnership and influencer marketing borrow someone else's audience: a creator, a complementary business, an affiliate who is paid on results. You pay for performance rather than for impressions, which makes it attractive — but the partner's reputation becomes yours.
Referral programmes turn satisfied customers into a channel. A simple reward for a genuine introduction is usually the cheapest customer acquisition a small business has.
Outbound — cold email, direct messages, sales calls, B2B prospecting — is hard work that scales with effort. It is the right channel when your customers are few and valuable, and the wrong one when they are many and cheap.
Start from where your customer already spends attention, not from where you enjoy posting. Then filter by what you can sustain: a channel you cannot commit to for six months will only produce false evidence that it does not work.
Fit it to the business model. Low-value products need cheap, high-volume channels. High-value services justify direct outreach and partnerships. Marketplaces and app stores are distribution channels in their own right — someone else's traffic in exchange for a commission.
Then write it down: the two or three channels you will run, what each will cost per month, and the number you will judge them by.
Social Media
Where your customer already spends attention — the top of most funnels.
SEO & Blogging
Answering people who are already searching — slow to build, compounds for free.
Content & Video
Earning attention by being useful rather than paying for it.
Email Marketing
A list you own and can export — immune to algorithm changes.
WhatsApp Marketing
Where most Nigerian customers prefer to be reached and to buy.
Referral & Word of Mouth
Your customers as a channel — usually the cheapest acquisition you have.
Meta Ads
Paid social reach across Facebook and Instagram, with precise targeting.
Google Ads
Paid search that answers people actively looking for what you sell.
Retargeting
Reminding people who already visited or started a checkout — highly efficient.
Influencer & Affiliate
Borrowing an audience, paid on results rather than impressions.
Cold Outreach
Email, DM and calls — scales with effort, best for few high-value customers.
Marketplaces & App Stores
Someone else's traffic in exchange for a commission.
Real-world examples:
Everything decided over these twenty classes now goes onto one document: the Online Business Master Blueprint. It is the plan the Month 2 build phase will follow, and the standard against which you will judge every new idea for the next three months.
A blueprint is not a wish list. It is specific: this business, this customer, this product, these systems, these costs, these targets. If a line could belong to any business, it is not yet a plan.
Today we assemble it in four parts — the system end to end, the one-time build cost, the recurring operating cost, and the marketing and finance numbers.
Lay the business out as one chain: customer → marketing channel → website or app → AI sales system → lead capture → CRM → database → payment gateway → email, SMS and WhatsApp → analytics → automation → customer support.
Every link in that chain must name a tool you have chosen and an owner — a person, a contractor or a subscription. A link with no tool and no owner is where the business will quietly break.
Read it back to yourself as a customer would experience it, from first seeing your ad to receiving their order. Anywhere the chain has a gap, that is your next piece of work.
Keep these two lists strictly separate — confusing them is the fastest way to run out of money. Build costs happen once: website, web application, mobile app, backend, database, UI/UX, AI setup, integrations, testing, deployment, developers, designers, freelancers and contractors.
Operating costs recur every month whether you sell or not: hosting, AI usage, APIs, email, SMS, WhatsApp, CRM, software, payment processing, staff, support, marketing and accounting.
Add them up honestly, including the ones you would rather ignore. A business plan that only works if nothing goes wrong is not a plan — which is why the next line exists.
Budget the marketing as its own block: initial launch spend, content production, advertising, influencer and affiliate commissions — measured against the customer acquisition cost you established in the analytics session.
Then the total you need to start: development budget, operating budget, marketing budget and a contingency for the things you have not thought of yet. Contingency is not pessimism; it is what keeps a small problem from ending the business.
Finally, the targets: the revenue you are aiming for, the point at which monthly income covers monthly cost — break-even — and the number of customers that requires. Work backwards from break-even to a daily number of sales or leads. That is the figure you will actually manage the business by.
System Architecture
Customer → channel → site → AI sales → CRM → database → gateway → messaging → analytics → support.
One-Time Build Cost
Website, app, backend, database, design, integrations, testing, deployment and the people who build it.
Recurring Operating Cost
Hosting, AI, APIs, messaging, CRM, software, fees, staff, marketing and accounting — every month.
Startup Capital
Build + operating + marketing, plus a contingency for what you have not thought of.
Revenue Target
The income you are aiming for, stated as a number.
Break-Even
The point where monthly income covers monthly cost — and the customers that requires.
This is a filling-in exercise, not an essay. Take one page and answer eight short lines about your business. One sentence per line is enough — write it the way you would explain it to a friend.
A small food business: Mama Ada Kitchen, selling jollof rice packs online in Lagos
© 2026 Regonet AI · 3-Month Business Development Program · Combined Session 3 — Days 16, 17, 18, 19 & 20