I come from an engineering background. My world was always about problem-solving, logic, and building things that work. Business was never part of the plan until I got an idea I couldn’t ignore.

That idea was clear in my head, but everything else was blank.

I could explain the product architecture in one whiteboard session. I could not answer basic questions like:

  • Should I register first or validate first?
  • What filings are mandatory in month one?
  • What can wait until we have real users?

I had an idea, not a business plan

My first instinct was technical. I kept asking:

  • Does this solve a real problem?
  • Can I build a working version quickly?
  • Can I test it with real users?

Those were good questions. They were not enough.

Very quickly, I learned that a startup is two systems running at the same time:

  1. Product system: build, test, iterate.
  2. Business system: register, comply, operate.

I only knew the first one.

The moment it felt real

The shift happened when someone asked me a simple question: “If this works, who is legally responsible?”

I did not have an answer.

That question changed how I looked at everything. Until then, “startup” felt like writing code and getting users. After that, it felt like building something that could survive in the real world.

Learning from zero

I started learning like I debug software.

Small scope. One topic at a time. Notes after every session.

My weekly loop looked like this:

  1. Pick one unknown topic (for example: incorporation).
  2. Read 3 to 5 reliable sources.
  3. Write a one-page summary in plain language.
  4. Ask one experienced person where I am wrong.
  5. Update the summary and keep going.

This removed a lot of panic. I still felt uncertain, but the uncertainty became manageable.

Asking for help

As an engineering student, I was used to solving problems alone. In startup work, that approach is expensive.

One 20-minute call with someone experienced saved me from weeks of random reading more than once. The pattern repeated enough times that I changed my default behavior: ask earlier.

The fear of mistakes

This part was hard. Every step felt high stakes.

I worried about missing filings, misunderstanding rules, or making decisions that would hurt us later. I wanted complete clarity before moving.

But complete clarity never arrived.

What worked was taking small reversible steps, then correcting quickly.

What I learned

  • An idea is only the starting point.
  • Business skills are learnable, even from zero.
  • Confusion is normal, not a sign to quit.
  • Progress usually looks messy while you are inside it.

Final thoughts

If you are an engineering student with one strong idea and no business background, you are not behind. You are at the beginning.

Start with the question in front of you. Learn one layer at a time. Ship small, ask for help, and keep moving.

That is what I am doing.