“How much will it cost?” is usually the first question in any software project, and the honest answer is “it depends”. This article explains what it depends on, so you can read an estimate critically and compare proposals on more than the final price.
The formula behind every estimate
Whatever pricing model appears in the contract, the cost of custom software comes down to one calculation:
people × time × rate, plus the costs that continue after launch.
- People: how many developers, designers and project managers, and how experienced they are.
- Time: how many weeks of work the scope requires, including discovery, testing and putting the software live.
- Rate: the daily or monthly cost of each person, which depends on experience and on the market the team works in.
Rates in Morocco are generally lower than in Western Europe or North America for a similar level of experience, which is one reason companies from those markets work with Moroccan teams. But the rate is the factor you control least and the one that matters least. Scope and execution change the total far more.
What drives the scope
Two projects that are both described as “a management app” can differ in cost by a factor of ten. The main drivers:
- Number of user types and workflows. Each type of user (administrator, manager, field staff, customer) multiplies the screens, permissions and special cases.
- Connections to other software. Payment providers, accounting software, government services, ERPs and old databases are often the riskiest part of a project, because they depend on systems you do not control.
- Platforms. A web application, a mobile app, a desktop application, or all three.
- Data migration. Moving years of data out of spreadsheets or an old system is a project in itself.
- Offline use, real-time features and high traffic. Each one adds design and testing work.
- Languages and right-to-left support. A French and Arabic interface needs more than translated text: layouts, dates, numbers and search all need attention.
- Compliance and security. Handling personal data under Morocco’s Law 09-08, or the GDPR for European users, adds process and design work.
Common project sizes
Rather than invented average prices, here are three common project sizes. Multiply the durations by the rates you are quoted to get a first idea of the budget.
| Size | Typical scope | Typical team | Typical duration |
|---|---|---|---|
| Focused tool | One or two workflows, one type of user, a few connections to other software | 1 to 2 developers | 4 to 8 weeks |
| Business platform | Several user types, reporting, 2 to 4 connections, web plus mobile or desktop | 2 to 4 people | 3 to 6 months |
| Product or SaaS | Many customer accounts, billing, public users, scale and security requirements | 4 people or more | 6 months, then ongoing |
These durations include discovery, testing and launch, not just coding.
How to read an estimate
A reliable estimate is a document, not just a number. Look for:
- A breakdown by feature, with ranges. A single figure suggests a precision that does not exist.
- Clearly stated assumptions. “The accounting software offers an API” is an assumption that can double a budget if it turns out to be wrong.
- A list of unknowns and how they will be resolved, often through a short, paid discovery phase.
- What is not included. Content entry, data migration, app store fees, hosting and third-party licences are often left out.
- The cost of running the system afterwards.
If two proposals are very far apart, the difference is almost always in the assumptions. Ask each provider to list theirs.
Five ways to keep the budget under control
- Pay for discovery first. A few weeks of workshops and planning, delivered as a written scope, is the cheapest insurance you can buy.
- Release a small, complete piece early. One complete workflow in real use teaches you more than months of specifications.
- Split the project into phases. Each phase has its own budget and a useful result, so you can stop, adjust or continue.
- Say no to “while we’re at it”. Keep a list of ideas for later phases instead of growing the current one.
- Own your code and accounts from day one. It keeps your options open and prevents costly lock-in.
In short
The price of custom software in Morocco, as anywhere else, depends on the scope and the quality of execution much more than on the hourly rate. Treat estimates as a set of assumptions to question, invest in discovery, and plan for life after launch.
If you would like a second opinion on a proposal you have received, or a first estimate for your own project, tell us what you are building.