Most mid-sized companies that decide to build a custom app start with a vendor demo or a developer's resume. The projects that stall usually did not run short on code. They ran short on one or two roles nobody thought to staff.
This is a practical look at who needs to be in the room, which seats you hire permanently, and which you can fill on contract in Canada or the US.
Start with the person who owns the problem
Before anyone writes code, someone has to decide what the app is for, who uses it and what a good result looks like. That is a product owner or a business analyst, and it is the seat most often left empty.
In a manufacturer or distributor, this is often an operations lead who knows the workflow cold. Give that person real time on the project, not a few hours a week on top of a full job. If nobody internal can do it, a contract business analyst for 3 to 6 months is a sensible way to get requirements written down before development money is spent.
The test is simple. If two stakeholders describe the app differently, you are not ready to hire developers.
Design is part of the build, not a coat of paint
Internal tools get a pass on design more than they should. A warehouse scanner screen or a quoting form that takes 11 clicks will be worked around, and then your data is no good.
You need someone who can map how people actually do the task and turn that into screens. On a small project one designer can cover both the flow and the visuals. On a customer-facing product, expect to want both skills, and to want them early.
The engineering core
The shape of the team depends on scope, but the common roles are:
- Front-end developers, who build what users see
- Back-end developers, who build the logic, data handling and integrations
- Full-stack developers, who cover both and suit a first version
- A cloud or solutions architect, once the app has to connect to your ERP, CRM or accounting system
For a first release, one or two strong full-stack developers and a part-time architect will often beat a large team with many handoffs. Hire for judgement on trade-offs between speed, cost to maintain and ability to scale, not just for a language on a resume.
Testing and security from week one
Quality assurance and security are often booked for the end of the project, which is when fixes cost the most. The US National Institute of Standards and Technology publishes a Secure Software Development Framework that builds security into the whole development cycle, and it is a reasonable standard to hold a team to.
A tester working alongside developers catches problems while they are cheap. If the app touches customer records, payments, health information or employee data, add someone with identity and access management experience, and check what privacy rules apply in your province or state.
Decide on AI early
If the plan includes search, assistants, forecasting or automation, the team changes. Ordinary developers are rarely enough. Depending on the goal you may need:
- A data engineer to clean and organize the data the feature depends on
- A machine learning engineer to build, deploy and monitor models
- An AI architect to decide how the feature connects to your systems
Most mid-sized employers should not hire all three permanently. Data engineering is usually the first and most useful permanent hire, because poor data sinks AI features regardless of the model. Model work is often a good fit for contract specialists.
Someone has to run the schedule
A project manager keeps scope, budget and dependencies in view. Without one, developers absorb every new request and the date slips quietly. On a small build, a strong product owner can double as the coordinator. Once you have outside partners, several teams or a hard launch date, a dedicated project manager pays for itself.
Hire, borrow or contract
| Role | Usually best as |
|---|---|
| Product owner | Internal, with a contract analyst to support |
| Designer | Contract, unless you build often |
| Full-stack developers | Mix of permanent and contract |
| Architect | Contract or part-time |
| QA and security | Contract for the build, permanent as the app matures |
| Data engineer | Permanent |
| Project manager | Contract for the project |
The rule behind the table is that you hire permanently for what you will need every year, and you contract for skills that peak during the build. Plan for who maintains the app after launch, or the first departure of a contractor leaves you with code nobody understands.
What to do next
Write down the capabilities your project needs, then mark each as already in-house, needed for the build only, or needed for the long term. The gaps in that list are your hiring plan, and the order you fill them in matters more than the total headcount.
A Traverse recruiter can help you fill those seats, whether that is a contract analyst for the first 90 days or a permanent data engineer.