You've never commissioned custom software before. It feels like a big, risky step.
This guide is for you.
It's Okay to Be New
Everyone's first custom software project is a learning experience. The good news:
- Thousands of businesses do this successfully every year
- The process is well-established
- Good partners guide you through it
- You don't need to be technical
Your job is to know your business. Their job is to know technology.
The Journey Overview
Phase 1: Discovery
What happens: Understanding the problem and defining the solution.
Your role:
- Explain your business and challenges
- Answer questions
- Provide access to information
- Make decisions about priorities
Duration: 1-4 weeks depending on complexity
Phase 2: Design
What happens: Creating the blueprint for the solution.
Your role:
- Review wireframes and mockups
- Provide feedback on workflows
- Confirm the design matches your needs
- Approve before building begins
Duration: 1-4 weeks
Phase 3: Development
What happens: Actually building the software.
Your role:
- Attend demos (every 1-2 weeks)
- Provide feedback on working software
- Answer questions as they arise
- Make decisions on trade-offs
Duration: 2-6 months typically
Phase 4: Launch
What happens: Going live with real users.
Your role:
- Final acceptance testing
- Coordinate with your team
- Prepare for the change
- Support your users
Duration: 1-2 weeks
Phase 5: After Launch
What happens: Supporting the live system and making improvements.
Your role:
- Report issues
- Prioritize enhancements
- Manage ongoing relationship
Duration: Ongoing
Key Concepts to Understand
Requirements
What the software needs to do. Start with:
- Who will use it?
- What will they do with it?
- What problems does it solve?
- How will you know if it works?
You don't need to write technical specifications. Just describe your needs in your own words.
Scope
What's included in the project. Everything has cost and time implications.
Learn to distinguish:
- Must have: Can't launch without it
- Should have: Important but not blocking
- Nice to have: Would be great, can wait
Iterations
Software is built in cycles. You'll see work-in-progress frequently. It will look incomplete because it is. That's normal and good — it lets you provide feedback early.
Change Requests
When you ask for something different from what was agreed. These affect timeline and budget.
Not bad — learning happens. But understand the process and impact.
Acceptance
Formally agreeing that the software meets requirements. You'll be asked to accept deliverables at key points.
Take it seriously. Review carefully before accepting.
Common First-Timer Mistakes
Mistake 1: Unclear Requirements
"I'll know it when I see it" doesn't work.
Better: Spend time on discovery. Be specific about problems. Ask questions until you understand what you're getting.
Mistake 2: Scope Creep
Adding things without understanding impact.
Better: Understand change request process. Budget contingency for changes. Prioritize ruthlessly.
Mistake 3: Being Too Busy
Not attending demos. Slow to respond. Decisions delayed.
Better: Block time for the project. Treat it as a priority. Respond promptly.
Mistake 4: Unclear Decision Authority
"I need to check with my boss" on everything.
Better: Establish who decides what upfront. Get buy-in before starting.
Mistake 5: Expecting Perfection
Software will have bugs. First version won't have everything.
Better: Plan for iteration. Budget for enhancements. Expect some issues.
Mistake 6: Focusing Only on Features
Features are just part of the picture.
Better: Also think about usability, reliability, security, maintenance, support.
Questions You Should Ask
Before starting:
- What does success look like?
- What's the realistic budget and timeline?
- Who needs to be involved?
- What happens after launch?
During vendor selection:
- Have you done similar projects?
- Who will actually work on this?
- How will we communicate?
- What happens if things go wrong?
During development:
- Are we on track?
- Any concerns or risks?
- What decisions do you need from me?
Finding the Right Partner
For your first project, prioritize:
-
Communication: You'll need guidance. They should explain things clearly.
-
Relevant experience: They've done similar things before.
-
Cultural fit: You'll work closely. Relationship matters.
-
Right size: A small project doesn't need a huge agency. A complex project needs resources.
-
Patience with questions: First-timers have lots of questions. Good partners welcome them.
Budget Expectations
Simple internal tool: $5,000-20,000 Small business application: $20,000-50,000 Medium complexity: $50,000-150,000
Add 15-25% contingency for unknowns.
Budget for ongoing costs (hosting, support, maintenance).
Timeline Expectations
Simple tool: 4-8 weeks Small application: 2-4 months Medium complexity: 4-6+ months
Discovery and design add to this.
Things usually take longer than initially estimated. Plan accordingly.
Your Responsibilities
For the project to succeed, you need to:
- Be available and responsive
- Provide clear requirements
- Make decisions promptly
- Attend demos and provide feedback
- Test the software before accepting
- Prepare your team for change
You're not just buying a product — you're participating in building it.
It Gets Easier
Your first project is the hardest. After that:
- You know what to expect
- You know what questions to ask
- You understand the process
- You can evaluate vendors better
- You're a better partner
The first one is an investment in capability, not just software.
Ready for your first project? We'll guide you through it