From first sale to real company

Build income. Then build the business.

Start with what you already have, make the first honest sale and learn each part of building something that can grow. No magic shortcut—just the next useful step.

Start here

What are you trying to do now?

Choose the closest position. You only need the next useful step—not the entire business journey at once.

Where am I now? Check your stage

Tick only milestones that are already true. Your first unchecked milestone is the evidence to build next—not a reason to rush ahead.

Start with what you have

Build your first seven-day plan

Use your real position—time, belongings, experience and safe starting money. The result gives you one route and seven actions, not a prediction of earnings.

Not sure? Answer six questions for a seven-day plan
Do the work, one step at a time

A route you can actually follow

Use the example to get started, fill in your own answers and tick off what you have done. Your notes stay in this browser; this page does not send them anywhere.

Choose a different route
App idea

Make one useful app, then put it online

Your first milestone: a stranger can open a link on their phone, complete one task and get a result. That is more valuable than a beautiful mock-up.

1. Define the one-screen version

Fill in these three lines before asking AI to write code. If the result cannot be described clearly, simplify the idea.

Example: “A seller uploads an item photo → sees an editable listing draft → copies the text.” No accounts, dashboard or payments in version one.

2. Turn the idea into an exact build request

Copy this brief into an AI coding tool and replace the bracketed parts with your answers. Ask for a complete file, not isolated snippets you must assemble on a phone.

Build a mobile-first, single-page HTML app for [audience]. The user enters [input] and receives [output]. Include input validation, a loading state if needed, a clear error message, and a copy button for the result. Keep the CSS and JavaScript in index.html. List every extra file or service required. Do not put API keys in browser code.

3. Test, publish, connect

  1. Test locally. Open index.html on a phone. Try a normal input, an empty input and a wrong input. Check buttons and links. If the app needs camera access, an API or server functions, local-file testing may not prove those parts work.
  2. Find the build output. For a plain HTML app, put index.html and referenced images together in one folder. A framework app may instead produce an output folder after a build. Upload that output, not an arbitrary source folder.
  3. Deploy to a host. On Netlify, use the manual deploy area for the project folder and open the resulting netlify.app address. Check the live mobile flow before connecting a purchased domain.
  4. Connect your domain. Add the domain in the host's domain settings, then copy the DNS instructions it gives for your particular setup. Check both the root domain and www, and wait for HTTPS to work. DNS changes can take time; do not guess record values from another site.
  5. Protect secrets. If your app calls a paid AI service, send that request through a server-side function using an environment variable. A key in index.html is visible to visitors.
Execution playbook: from folder to working public app

Run these checks in order

  1. Prove one complete flow locally without accounts, subscriptions or optional features.
  2. List every dependency: hosting, domain, server function, API, database, email and payment provider. Mark which ones can charge when nobody buys.
  3. Deploy the complete output folder and test the temporary host address before changing DNS.
  4. Connect the domain, wait for HTTPS, then test normal, empty and failed inputs on another phone.
  5. Add analytics and record successful completions—not just visits—before deciding what to build next.

Starting cost: a simple static test can use free hosting. A domain, paid API, email, database or payment service can add recurring or usage costs; price the whole working system, not only the webpage.

Move on when: somebody outside the build process completes the live task without instructions, and errors do not expose a secret or charge the user twice.

What the “AI builds your app” pitch skips

AI can draft code. You still own the test cases, hosting, domain, DNS, privacy, payments, API costs and support. Stop adding features until the first flow works end to end.

Online store

Prove one product can sell at a margin

Your first milestone: one product listing, one tested checkout and a clear figure for what you keep from an order before overhead and tax.

1. Decide what the buyer is actually getting

Example: “An A3 custom rugby team print delivered in the US within the displayed delivery window.” Write down size, material, personalisation, what the buyer supplies and who fixes a printing error.

2. Calculate one order, not just revenue

Enter estimates in one currency. The result is before monthly subscriptions, tax, refunds and your time. Use a supplier quote where you can; never treat a placeholder as a real cost.

Enter a sale price to see the per-order result.

Illustration only: 45 − 18 − 7 − 2 − 5 = 13 per order before other costs. If you cannot explain how buyers arrive without paid ads, set advertising to 0 for the first test and revisit it later.

3. Build a page you can take an order from

  1. Show the product clearly. Use genuine images or an accurately labelled example; give size, material, variations, delivery estimate and price.
  2. Set the mechanics. Configure payment, delivery area and charges, confirmation email, contact details and the returns or cancellation process relevant to your product and market.
  3. Test an order yourself. Complete checkout on a phone. Verify the correct price, confirmation, supplier notification and refund path. For print on demand, check the product is actually linked to the fulfilment provider; a storefront listing alone sends no print job.
  4. Start small. Reach a handful of likely buyers and record visits, questions, orders, refunds and your time. Improve the offer before expanding the catalogue.
Execution playbook: launch one product safely

Choose the simplest checkout that proves demand

  1. Write the product specification and obtain one real delivered-cost quote for the buyer’s location.
  2. Choose either a marketplace with existing buyers or a standalone store you must attract buyers to. Do not pay for both before the first test needs them.
  3. Publish one product with accurate photographs, delivery, cancellation/return information and a contact route.
  4. Place and refund a test order. Confirm that stock or the print-on-demand variant is actually connected.
  5. Send the offer to a small relevant audience and record visits, checkout starts, sales, refunds and support time.

Budget for: product or sample, packaging, delivery, platform/payment fees, returns, tax and possibly a monthly storefront subscription. Verify current prices before committing.

Move on when: a genuine customer receives the correct item and the money left after variable costs matches your estimate.

Affiliate content

Publish a useful comparison before asking for clicks

Your first milestone: one original guide that helps a specific reader choose, with honest limitations and a working disclosure.

1. Pick a buyer question you can answer

Example: “Which tyre inflator suits someone who needs to top up a car tyre at home?” Compare power source, reach, pressure display, storage and limitations. Do not claim a product was tested unless you tested it.

2. Apply and set up the links correctly

  1. Pick your market. If most readers buy in the US, start with the US Associates programme and US product pages. Check the separate UK programme if you serve UK buyers too.
  2. Check the official eligibility page. Apply using the real website or other eligible channel where your original content is already published. Amazon reviews applications against its current requirements.
  3. Use the provided link format. Create tagged links with Amazon’s authorised tools. Put them beside the comparison they support, not on an empty link farm.
  4. Disclose the relationship. Place a clear affiliate notice where readers will see it, including Amazon’s required Associate identification statement. Follow the current programme rules for content and links.
  5. Review the page. Click every link, check the destination country and product, and revisit the guide when stock, models or terms change.
Execution playbook: earn the first attributable commission

Content comes before the application

  1. Choose one buyer question and confirm that people search, ask or compare before purchasing.
  2. Publish an original answer that is useful without an affiliate link and identifies drawbacks as well as benefits.
  3. Apply through the programme’s official site using the channel where that content is already public.
  4. If approved, use authorised link tools and the required disclosure. Never copy another publisher’s review.
  5. Measure page visits, outbound clicks and qualifying actions separately. Update or remove stale recommendations.

Starting cost: joining a legitimate affiliate programme should not require buying a starter pack. A website/domain and creating original evidence may cost money; commissions and approval rules can change.

Move on when: the page attracts relevant readers and produces a tracked qualifying action—not merely when links have been added.

What gets paid

A click is not a payment. Amazon describes earnings from qualifying purchases or actions under its current terms. Write the guide for the reader first; traffic and conversions have to follow.

Sell a service

Turn a skill into an offer someone can understand

Your first milestone: send five tailored offers for one defined result. “I do websites” is vague; “I rebuild your one-page menu so it works on phones for $___” can be evaluated.

1. Build the offer backwards from the result

Example: “For independent cafés, I photograph five best-selling items and deliver ten edited, web-ready images within four days. One reshoot for a technical fault is included. Food, travel beyond five miles and ongoing social posting are not included.”

2. Set a price that includes the invisible work

Estimate the sales conversation, preparation, travel, delivery, revisions, platform fees and materials as well as the obvious job. Price = costs + payment for your total time + a buffer for normal problems. Check tax, insurance, licences and consumer rules that apply to your location and service.

3. Send a short proposal based on evidence

Template: “Hi [name]—I noticed [specific, genuine observation]. I help [type of business] achieve [result]. I can deliver [scope] by [time] for [price]. Here is a relevant example: [link/photo]. If that would be useful, I can confirm the details in a short written agreement.”

Personalise the observation. Never pretend you found a problem you did not check. Keep proof small and relevant; a sample should demonstrate the result, not become hours of unpaid custom work.

Execution playbook: complete the first paid service
  1. Choose one type of customer, one result and one delivery format you can produce reliably.
  2. Create a small proof example and write the boundaries, deadline, price, payment point and revision limit.
  3. Check insurance, licences, tax and consumer requirements relevant to the actual service and location.
  4. Contact five suitable prospects individually. Confirm scope in writing before beginning and issue a record of payment appropriate to your jurisdiction.
  5. Deliver, request a specific acceptance or correction, record every hour and ask permission before using the work as a case study.

Budget for: materials, travel, payment fees, software, insurance, tax and unpaid sales/admin time. Do not price only the visible delivery hour.

Move on when: the client accepts the agreed result, payment clears and you can explain what must change before repeating the same offer.

If nobody replies

Do not add ten more services. Check whether the buyer is specific, the result matters, the example proves it and the message reached the right person. Change one of those variables and test five more.

Remote employment

Search for a role, not “anything remote”

Your first milestone: submit three tailored applications for one type of role you can support with evidence.

1. Translate experience into proof

Choose a role first—customer support, scheduling, sales admin, technical support or another defined job. Then match evidence from work you have already done.

Weak: “Good communicator.” Stronger: “Explained technical options to customers, recorded work accurately and resolved complaints during busy workshop shifts.”

2. Verify each vacancy before applying

Find the same vacancy on the employer’s real website. Check the legal employer name, permitted work location, hours, employment status and how interviews are conducted. Be wary of text-only interviews, personal email domains, instant offers or instructions to buy equipment using money they send.

Execution playbook: submit verified applications
  1. Select one job title and collect ten real vacancies to identify repeated skills, hours and location requirements.
  2. Rewrite the CV opening and evidence for that role; do not claim tools or experience you cannot discuss at interview.
  3. Find each vacancy on the employer’s official careers site and confirm the recruiter’s email domain.
  4. Submit three tailored applications and save the vacancy, answers, date and expected next step.
  5. Prepare two examples using situation, action and result, then verify any interview invitation independently.

Starting cost: applications should not require payment. Normal costs may include internet, suitable interview equipment or an optional qualification you have independently verified.

Move on when: three genuine applications are recorded and you can see whether the problem is targeting, evidence, application quality or interview skill.

Important distinction

A remote role can still require residence in a particular country, fixed shifts or employee eligibility. Read the location and contract details before spending time applying.

Reselling

Learn with items you already own

Your first milestone: publish five accurate listings and complete one profitable sale before buying stock.

1. Price from sold evidence

Identify the exact brand, model, size and condition. Look for recently sold comparable items—not ambitious asking prices. Compare the same condition and include delivery.

Optional identification and listing aid: If you do not know exactly what an item is, HowMuchForThis ↗ can help produce an estimated price and editable listing draft from a photo. Confirm the item, correct any mistakes and compare the estimate with actual sold listings before publishing.

2. Write a listing that prevents surprises

Template: [Exact item and model] — [condition]. Includes [contents]. Tested by [honest method]. Known marks or faults: [details]. Measurements: [dimensions]. Collection/postage: [method and timeframe].

3. Record actual profit

Profit = sale price − item cost − platform/payment fees − packaging − postage − refund or repair allowance. Record time separately. Only buy stock after completed sales show that the margin and sell-through time are acceptable.

Execution playbook: complete the first sale
  1. Choose five items you own, can identify and can safely deliver. Clean and test them without hiding defects.
  2. Use sold—not listed—comparables, then calculate platform, payment, packaging and delivery costs.
  3. Photograph the actual item, labels, accessories, scale and every fault; write collection or delivery terms clearly.
  4. Publish on one suitable marketplace and keep payment and messages within its official process.
  5. After collection or tracked delivery, record cleared proceeds, all costs, time and any buyer issue.

Starting cost: use items already owned so the first lesson is not tied up in stock. Packaging, delivery and marketplace fees still count.

Move on when: one buyer has the accurately described item, payment has cleared and the completed-sales record shows the actual result.

Do not scale from one lucky sale

A profitable item does not prove a repeatable supply. Test a small batch, keep receipts and understand the marketplace, tax and consumer obligations that apply when selling as a business.

Digital product

Package a repeated solution once

Your first milestone: one buyer uses the product to finish a real task without needing you to explain every step.

1. Validate the task before making the file

Look for repeated questions, messy spreadsheets, duplicated admin or instructions people keep recreating. Ask potential users to show how they do the task now and what a mistake costs.

2. Make the minimum useful product

Choose the simplest format that completes the job: checklist, calculator, template, printable, prompt workflow or short guide. Include an example, instructions and the limits of what it does.

3. Price the test

Calculate break-even sales: your creation and setup costs divided by the amount left per sale after fees. Treat your time separately so “free to make” does not mean free.

Execution playbook: deliver the first paid copy
  1. Observe five target users doing the task and identify the same costly or frustrating step in at least three cases.
  2. Build the smallest template, calculator, checklist or guide that completes that step; include instructions and a worked example.
  3. Watch one user try it without coaching and repair the first point of confusion.
  4. Choose a delivery route that handles payment and gives the buyer the correct file. State format, compatibility, updates, support and refund terms before checkout.
  5. Place a test order, open the delivered file on another device, refund it, then invite a small relevant audience.

Budget for: creation time, design/software, payment or marketplace fees, tax, refunds, customer support and future compatibility updates.

Move on when: a target user pays, receives the correct product and completes the promised task without private coaching.

Do not start with fifty templates

Sell or test one. A catalogue multiplies maintenance and support; it does not create demand.

The first-customer engine

Turn a route into a paying customer

Use this with a service, product, app or store. It separates a reach problem from an offer, trust or price problem so you change the right thing instead of starting another idea.

Open the first-customer system

1. Build a list of 20 suitable prospects

A prospect is not “anyone who might want it.” Record a real reason the person or business could need this result now.

Local example: An independent café has an unreadable mobile menu. Offer one fixed menu rebuild; do not pitch websites, photography and social media together.

2. Make one small, specific offer

Lead with a truthful observation, the result, boundary, time and price. Ask for a decision or conversation—not a vague “let me know.”

Message structure: “I noticed [specific evidence]. I can deliver [defined result] by [time] for [price]. It includes [scope] and does not include [boundary]. Here is relevant proof: [example]. Would that solve the problem?”

3. Diagnose the pipeline

Enter cumulative totals from one consistent test. A conversation means a real reply or discussion; an offer states a scope and price.

Enter your totals to identify the first blockage.

These thresholds diagnose a small test; they are prompts to inspect evidence, not universal conversion benchmarks.

4. Complete the transaction properly

5. Turn delivery into proof

Ask permission. A useful case study shows the starting problem, what was delivered and an observable result; it does not invent a dramatic percentage or expose private customer information.

6. Decide using evidence

  • No conversations: inspect targeting, contact route and opening message.
  • Conversations but no offers: clarify the need, result and qualification questions.
  • Offers but no sales: inspect proof, risk, urgency, price and whether the buyer can decide.
  • Sales but no worthwhile margin: change price, scope, delivery method or stop. More volume magnifies a loss.

Move on when: the same defined offer has produced more than one properly completed, economically sensible sale—or the evidence clearly justifies changing it.

Your work

Save or clear your answers

The worksheets are already inside each route. Copy your completed notes, print them or clear the answers saved on this device.

Your entries remain in this browser unless you copy, print or clear its site data.

After the first customers

Turn earning into an operation

Registration does not create a business. Evidence of demand comes first; structure, records and systems make it durable.

Open the business, structure, systems and growth stages
Stage 05 / Business operation

Know what happens from enquiry to money kept

Your milestone: you can trace one real sale from customer enquiry through delivery, costs, payment, records and follow-up.

Map one complete sale

Write the business on one page

This is an operating brief, not a prediction dressed up as a forty-page plan. Use evidence from customers and completed sales.

Cash-flow reality check

Use one currency and a normal month—not the best month imagined. “Gross margin coming in” means sales minus the direct cost of fulfilling those sales. This is a planning snapshot, not tax or accounting advice.

Enter the four figures to see the monthly position and estimated runway.

Exclude money required for tax, refunds or bills already due from “cash available.” Update the figures when actual money arrives or leaves; an unpaid invoice is not cash.

Protect the business outside the platform

A marketplace, social account or payment processor is a route to customers—not the business itself. Keep lawful records without scraping or exporting customer data against platform terms.

Ready for the next stage when

Customers have paid, the margin survives real costs and you can explain how orders are accepted, fulfilled, recorded and corrected.

Stage 06 / Structure

Choose a structure for a reason

Your milestone: write down why the structure suits your ownership, liability, tax position and plans—then verify it with the official authority or a qualified adviser.

Company-readiness brief

Use the official route for your location

The checklist changes by country, state and activity. Choose a starting route below, then confirm local licences and professional advice where the decision carries legal or tax consequences.

United States starting sequence
  • Identify the state and locality where the business will operate.
  • Compare structures against ownership, liability, tax and funding needs.
  • Check state and local registration, name, licence and permit requirements.
  • Use the IRS directly to check whether an EIN is needed and apply free.
  • Set up appropriate banking, records and insurance before scaling activity.
Do not register for appearance

A company can add filings, costs and responsibilities. The right time and structure depend on facts that a generic website cannot decide for an individual.

Stage 07 / Systems

Write the first procedure someone else could follow

Your milestone: one repeated task has a tested checklist, owner, quality standard and recovery step.

One-page operating procedure

Delegation and first-hire gate

Delegation is not simply paying somebody less than the sale price. The work needs a stable process, lawful engagement, controlled access, supervision and an economic reason.

Systemise the bottleneck first

Do not automate every task. Start with repeated work where delay or inconsistency harms customers or cash flow.

Stage 08 / Growth

Make sure growth improves the business

Your milestone: identify the actual constraint and prove that spending money or adding capacity addresses it.

Growth decision

Funding ladder: buy evidence, not appearance

  1. Remove the need. Test whether a smaller scope, rented tool, manual process or supplier sample proves the same assumption.
  2. Use customer-backed evidence. Deposits, pre-orders or signed commitments can support demand only when the terms are clear and delivery is realistic.
  3. Reinvest earned margin. Preserve tax, refund and essential cash before using retained profit.
  4. Compare external finance. Model repayment, interest, security, ownership surrendered and the downside if the expected growth does not happen.
More revenue can create less cash

Stock, wages, advertising and longer payment terms may require cash before the customer pays. Model the timing, not only the sales total.

How this site works

Practical guidance with the catches included

Dollar Dominator is an independent starting-point resource. It does not promise income, sell jobs or rank a route because it sounds exciting.

Editorial method

What earns a place here

A route must lead to a defined action, disclose important costs and uncertainty, and give the visitor a way to test it on a small scale. Provider requirements and fees can change, so official terms remain the final source.

Privacy

Your worksheet entries stay on your device

This version stores worksheet answers and completed milestones in your browser so they remain after the page closes. They are not submitted to Dollar Dominator. Clearing site data removes them. External providers have their own privacy policies.

Commercial disclosure

Links should never change the conclusion

Some future links may earn Dollar Dominator a commission without changing the visitor’s price. Any such relationship must be labelled near the relevant link. Inclusion is not an endorsement or a guarantee of earnings.

Safety

Income is not speculation

Trading, crypto and gambling are not presented as dependable income routes. Never deposit money to unlock work, move money for a supposed employer or rely on earnings you have not verified.