Skip to main content

Launching Alongside a Day Job

Sustainable Making · 10 min read ·

How to build and launch a product in the hours around paid work: protecting your time, checking your contract, choosing small goals and avoiding burnout.

Illustration: A two-colour riso collage of a clock face cut from paper with two slices peeled away, labelled Work and Making, in teal and orange

Most products that are launched start life in stolen hours. Early mornings before the commute, evenings after dinner, a quiet corner of a Saturday. If you have a job, a family or both, that is probably how yours will go too. That is not a disadvantage to apologise for. A steady income takes the panic out of the early months, and plenty of good products have come from people who kept their day jobs until the numbers said otherwise.

It does ask for a different approach, though. This guide covers the practical side: the questions to ask before you start, how to find and protect your hours, how to set goals that fit, and how to look after yourself on a long road.

First, check the paperwork

Before you spend a single evening on the project, spend an hour reading your employment contract. You are looking for three things.

Outside work. Some contracts require you to tell your employer about, or get permission for, other paid or business activities.

Intellectual property. Some contracts say that things you create belong to your employer, in some cases even outside working hours if they relate to the business. The detail varies a great deal.

Competition and confidentiality. Clauses that restrict working on products that compete with your employer's, or using information you learned at work.

The UK government's guidance on employment contracts and conditions explains what contracts typically contain and where to get advice. If any clause is unclear or you are building something close to your employer's field, get proper advice from an employment adviser or solicitor before you go further. A short conversation now can prevent a painful dispute later.

Good habits, whatever your contract says:

  • Use your own time, devices and accounts. Never use work hours, laptops, software licences or confidential information.
  • Keep your project separate in name, email and files.
  • Do not recruit colleagues into the project without thinking through the consequences.
  • Keep records of when and how you made things, in case questions arise.

If you decide to ask your employer, do it calmly and in writing, with a clear description of what you are doing and a statement that it will not involve their time, resources or confidential information.

Count your real hours

Most people overestimate. Open your calendar for last week and mark every hour you spent on anything related to the project. That is your real number, and it is probably smaller than you hoped.

Now decide what you can sustain. If you did six hours last week and had a quiet week, plan for six, maybe eight. You can add later. Planning for fifteen and delivering six leaves you feeling like a failure every week.

Time management advice is plentiful, but the core is simple: know how much time you have, choose what matters most and protect it.

Find the shape of your week

Look at when you actually have energy and quiet.

  • Mornings work for some people. A fixed hour before anyone else is up is uninterrupted.
  • Evenings are good for others, though tiredness is real.
  • Weekends can hold a longer block, if you protect them.
  • Commutes can be used for reading, planning or listening, if you do not drive.

Choose two or three regular blocks and treat them like appointments. Predictable hours beat heroic bursts.

Put them in your calendar. Tell the people who share your life when they are. Make the first minutes of each block easy to start: leave a note on where you stopped, so you can begin without hunting for your place.

Make goals that fit

A big goal in a small time budget leads to disappointment. Break it down.

Weekly goals. One or two things you can finish in your hours. "Write the first version of the sign-up page." "Talk to two users."

Monthly goals. One outcome. "Ten people have tried the product."

A stop-and-check date. A moment, say three months away, to ask whether to continue, change or stop.

Aim for small, visible progress. A thing finished is better than three things half-done.

Pick the right size of project

Some ideas fit part-time hours and some do not. A product that needs constant support or fast response may be hard to run alongside a job. One that is mostly self-service, with clear documentation and slow-moving requirements, is easier.

Think about:

  • Support load. How many messages will you get, and when?
  • Time zones. Customers in different places write at odd hours.
  • Dependencies. Does anything break if you are away for a week?
  • Scope. Can the first version be small enough to finish in the hours you have?

Choose or shape the idea to fit your life, not the other way around.

Protect your energy

Part-time making often runs on tiredness. Guard your health.

  • Sleep. Cutting sleep to find hours works for a few days and fails after that.
  • A full day off each week. No project, no checking messages.
  • Movement and food. Boring and essential.
  • Say no. To extra commitments that crowd out your blocks.
  • Notice warning signs. Irritability, dread at the thought of the project and lost interest are signals to rest and re-plan, not to push.

The NHS Every Mind Matters pages offer straightforward advice on looking after your mental wellbeing, including managing stress and sleep, and they are a good place to start if the load starts to feel heavy.

Tell people

Isolation is a risk in solo projects. Tell one or two people what you are doing, and ask them to check in. A weekly message to a friend, "this week I did X, next week I will do Y", is a quiet form of accountability that keeps you moving.

Tell the people you live with what you are doing and what you need from them, whether that is quiet at certain times or understanding on busy weeks. It is easier for them to be supportive when they know what is going on.

Keep the first version small

The less you try to do, the more likely you are to finish. A minimum viable product, by definition, has just enough features to be usable by early customers so that they can give feedback. For a part-time maker that is not only wise, it is the only way to ship.

Cut features without guilt. List what the product must do for the first user to get value, and put everything else on a "later" list. Revisit it after launch.

Launch week with a job

Launch week is intense, and you still have work. Plan for it.

  • Take leave if you can, even a day or two, so you can answer replies. Check that it is allowed and use your own time.
  • Schedule posts for your quiet hours, within the rules of each community.
  • Set expectations at home and with colleagues.
  • Keep it small. One place, one clear page, not five at once.
  • Check in at lunch and in the evening, not every ten minutes.

If something goes wrong while you are at work, remember that most problems can wait an hour. Do not use work time to fix them, if your contract says not to.

When to quit the job (or not)

There is no formula. Some people never leave their job and run a lovely side income. Some leave after a year of steady customers. A few leave early and succeed. Some leave and wish they had not.

Questions worth asking:

  • Does the product earn enough, reliably, to cover your essential costs, with a cushion?
  • Have you tested the demand with real customers, not only friends?
  • Do you have savings for the lean months?
  • Would you be happy to go back to employment if it fails?
  • What does the evidence of the past six months say?

Do not decide in the glow of a launch. Wait a few months and look at the numbers.

If the project becomes a business

If you start earning regularly, you may need to register, keep records and pay tax on the income. Government guidance explains how to register as a sole trader, for example, and what you need to keep track of. Look at the rules early so that tax does not become a surprise.

A weekly plan on a sticky note

  • Two or three fixed blocks.
  • One thing to finish.
  • One conversation with a user.
  • One full rest day.
  • One message to the person who is holding you accountable.

On this site

When you are ready to show your work, the submit page starts a listing, the launches page shows how others present their projects and the pricing page explains what is free and optional. The founders page introduces the two people behind this place, and the contact page reaches our support.

The short version

Check your employment contract first. Use your own time and tools, count your real hours and plan from those, choose regular blocks, set small goals, shape the project to your life, protect your sleep and your rest day, tell someone what you are doing and decide about quitting from evidence. Slow and steady gets launched.

Questions and answers

Can I launch a product while employed?
Many people do, but check your employment contract for clauses on outside work, intellectual property and competing activity before you start.
How many hours should I plan for?
The hours you can truly give each week, counted from what you did last week, not from what you hope to do.
Should I use work time or equipment?
No. Keep your project separate: your time, your devices and your accounts, to avoid disputes about ownership.
How do I avoid burnout?
Fix regular hours, take a full day off each week, keep goals small and tell someone how it is going.
When should I tell my employer?
It depends on your contract and relationship. If there is any doubt, read the terms and consider asking before you launch.

Sources

Related guides

Help centre