The first year: 30 days, 90 days, 12 months

The first year is not for pretending you own a company. It is for proving that a real customer, real workflow, real price, real delivery system, and real founder can survive contact with each other.

A young founder wants a grand plan because a grand plan feels like certainty. The market will not read it. The market will only respond to value, trust, timing, price, risk, and follow-through. Your first year therefore has four jobs: find, sell, improve, decide.

Do not resign, borrow, hire, or incorporate complexity merely to feel committed. Commitment is not measured by public declaration. It is measured by the number of uncomfortable, evidence-producing loops you close.

The first 30 days: find the problem

For one month, stop trying to “have a startup.” Build a map.

Choose a small, capacity-appropriate set of reachable markets. In Bengaluru, proximity can help: recruitment agencies, clinics, logistics operators, professional-services firms, property managers, manufacturers, education businesses, financial-services vendors, hospitality operators, or software/service companies. These are examples, not recommendations. Avoid regulated workflows unless you understand the responsibility and can test safely.

For each market, map:

• • a bounded list of organisations you can research properly;
• • the relevant user, process-owner, buyer, approver, and gatekeeper roles;
• • common workflows and tools;
• • visible workarounds, job posts, complaints, audits, reviews, or manual hand-offs;
• • buyer, budget, urgency, risk, and your capability;
• • warm paths to conversation.

Run problem interviews. Ask about the last real event, not imagined future behaviour. What happened? Who touched it? What did it cost? What did they try? What budget or authority exists? What risk would stop adoption? What would make this a priority now?

The output is not a deck. It is structured notes, repeated pain patterns, buyer map, and commitments: introductions, artifacts, second conversations, paid diagnostics, pilot reviews, or a clean no.

Days 31-90: sell the smallest responsible proof

Choose one segment and one problem. Write one offer:

• • before state;
• • promised after state;
• • mechanism;
• • scope and exclusions;
• • customer responsibilities;
• • safety/data/quality controls;
• • price and payment terms;
• • success metric;
• • stop/revise/continue date.

Show it to qualified buyers. Ask them to explain it back. Confusion is data. Objections are data. Silence after “interesting” is data. A buyer who will not risk money, time, access, or political capital is not yet a customer.

Build only what the proof requires. A manual service, diagnostic, prototype, technical spike, or limited pilot may be enough. Keep customer harm, data exposure, and promises bounded. Invoice cleanly. Collect. Deliver. Review. Repair. Change the process.

By day 90, you want one of three honest states:

Each is progress if it is honest.

Months 4-6: prove payment beyond politeness

The next job is commercial proof outside friends and family. Close and deliver the first paid pilot, then the next ones in the same or adjacent segment if evidence supports it. Define baseline, scope, quality, success, and customer responsibilities in writing. Track contribution after direct costs and founder time. Record reasons for wins and losses. Ask for referrals only when value was actually delivered.

Do not mistake a one-off rescue project for a repeatable business. The question is not “Can I make money once?” It is “Can I reach similar buyers, sell a similar promise, deliver with improving quality, collect cash, and create a reason for repeat, renewal, expansion, or referral?”

Months 7-9: make the machine less dependent on mood

Narrow the offer. Narrow the channel. Document qualification, discovery, proposal, onboarding, delivery, support, collection, and after-action review. Remove rework. Improve time to first value. Raise price or tighten scope only where customer value and conversion evidence support it. Establish weekly pipeline review and a 13-week cash forecast.

Test one delegation or automation only after the work is stable enough to describe. Do not automate confusion. Do not hire someone to inherit a process you cannot explain.

Months 10-12: decide from evidence

At the end of the year, review:

• • cash collected, contribution, runway, and protected obligations;
• • customer concentration, retention, referrals, and repeat use;
• • pipeline conversion, sales cycle, and reasons for loss;
• • delivery quality, rework, support burden, and founder dependency;
• • differentiated understanding, asset, relationship, or process created;
• • compliance, data, contracts, and trust risks;
• • founder health, family strain, and willingness to continue this market.

Then choose: double down, narrow further, change offer, change segment, return to research, keep as a side business, or close the experiment cleanly.

· GE chs. 40–41 · TABLE pp. 79–81 · SALES pp. 2–4 · ASC pp. 132–134. The dates are review cadence; activity volume must fit the market, risk, and founder capacity.