Owners hire a software company to get time back. Then, a month in, they are answering messages every evening, testing screens at midnight, and wondering how "outsourcing" became a second job.
Some of that time is unavoidable. Most of it is a sign of how the project was set up.
Key Takeaways
- Your time is heaviest at the start (planning) and the end (testing), and lightest in the middle.
- A well-run build needs a few hours from you in a normal week, plus focused testing at each milestone.
- The biggest time sink is unclear scope, because every gap becomes a question for you.
- Ask up front who manages the developers. If the answer is "you," price your time in.
Where Your Hours Go
| Phase | What you do | Typical time from you |
|---|---|---|
| Planning | Explain the business, answer questions, approve the scope | The heaviest phase: several hours a week for a week or two |
| Building | Review progress, answer occasional questions | A few hours a week |
| Milestone reviews | Test what was delivered against the agreed criteria | A focused half day or so per milestone |
| Launch | Final testing, content, go-live decisions | A heavy week |
| After launch | Report issues, plan next changes | An hour or two a week, then less |
These are rough ranges from how projects tend to go, not a promise. A project with many kinds of users or lots of your own content (prices, text, photos) will take more of your time.
The Three Time Sinks
1. Unclear scope. Every undefined detail becomes a question for you, one at a time, often at the worst moment. A clear plan up front replaces dozens of small interruptions with a few long conversations. See what is a discovery phase in software development.
2. Being the project manager. With many freelancers, and some agencies, you are the one keeping the developers on track. That means daily check-ins, prioritizing, and chasing. It is real work, and it is often the part owners did not budget for.
3. Constant meetings. Status calls that could have been a written update. A weekly written summary and a short demo usually beat daily calls for a non-technical owner.
How to Keep Your Time Small
- Ask who manages the developers. On our software factory projects, a dedicated project manager does, and you get weekly demos and written progress reports. You review; you do not run standups.
- Prefer written, async updates. You read them when it suits you. We default to Slack messages, written updates, and demo videos, and a live call is there when you want one.
- Batch your answers. Ask the builder to collect questions and send them once or twice a week.
- Review in blocks. Put milestone testing in your calendar as a fixed half day. A five-business-day review window, which is what we use, gives you room to do that properly.
- Name one decision-maker. If three people on your side can change their minds, the project slows and your time doubles.
A Concrete Version
Take an owner building a client portal over ten weeks, with four milestones.
- Weeks 1 to 2 (planning): two calls of about 90 minutes, plus reading and approving the scope. Around five hours.
- Weeks 3 to 9 (building): reading a weekly update and watching a short demo video, answering a batch of questions twice a week. About two hours a week, fourteen in total.
- Three milestone reviews during the build, about four hours each. Twelve hours.
- Week 10 (launch): content, final testing, go-live. About eight hours.
Total: roughly 40 hours over ten weeks, about four hours a week on average. Now compare the version where the owner manages two freelancers directly: a daily 20-minute check-in alone is over 16 hours across those ten weeks, before any testing, prioritizing, or chasing.
The Honest Counterpoint
You cannot outsource knowing your business. No builder, however well run, can decide your prices, your refund rules, or which customer exceptions matter. If an agency promises you will barely be involved, be careful: an owner who disappears for eight weeks often gets an app that is technically fine and wrong for the business. The goal is a few high-value hours, not zero hours.
Frequently Asked Questions
Can someone on my team handle this instead of me?
Yes, if they understand the process the app replaces and can make decisions. The person who does the work today is often the best reviewer.
What if I am too busy for milestone reviews?
Then the milestone review is the one thing to protect. Paying for work you have not tested is how problems reach launch. See how to review a software milestone before you pay.
Is a freelancer more work than an agency?
Usually, because you become the manager. Our comparison of freelancer vs agency to build your app covers the trade.
How do I know if the project needs more of my time?
If the builder is repeatedly waiting on your answers, it does. Ask for a list of open questions every week.
The Bottom Line
A well-set-up build asks for a few focused hours a week from you, heaviest at the start and at each milestone. If you want a clear plan before any build starts, the honest read gives you one in minutes. Related: how to build an app without a technical co-founder.
Roberto Espinoza is CEO of Ruzora, which builds custom software for business owners at a fixed price and places pre-vetted senior LATAM engineers with US teams. Get a free honest read on your idea.
