Custom web platform development in Algeria
A custom web platform costs from 500,000 DA at UpGrowth for a first version in service, with the firm price coming out of the cahier des charges. A marketplace, a portal, a customer area, a tool your users will pay to use: you have the project, and what is missing is whoever writes the first version, puts it online and keeps it standing once it starts being used. UpGrowth builds that first version, with the scope written down before we start and the code belonging to you at the end.
| Service | Published floor | Maximum delivery | What that floor covers |
|---|---|---|---|
| Custom web platform | 500,000 DA | 4 weeks | Written scoping, data model, accounts and permissions, the screens of the main journey, a dashboard, and deployment on hosting in your name. |
| Each amount is a floor and each delivery time a maximum for the scope described on the same row. The firm price and the firm delivery date come out of the cahier des charges: on a very specific development neither the price nor the time has a ceiling. | |||
1. A platform is not a website with more pages
A website presents. A platform makes people work together. The moment there are accounts, different roles, data the users create themselves and actions that trigger something for somebody else, you are no longer in the same category of project. What changes is not the graphic design: it is that the platform has to stay correct when two people act at the same time, when an operation fails halfway, and when somebody tries to see what they should not see.
Several roles, not one visitor
A buyer, a seller, a moderator, an administrator. Each sees and can do different things, and that boundary is the first thing to write down.
The data comes from users
It is no longer your own text. Somebody has to decide what is checked, what is moderated, what can be corrected and what can no longer be.
An action has consequences
An order, a booking, a payment, a cancellation. Each touches several people, and the platform has to stay coherent even when it is interrupted mid-way.
2. The families of platform people ask us for
The projects that reach us are more varied than the word marketplace suggests. These are the families we meet most often, with what genuinely separates one from another.
Marketplace
Several sellers, one shared catalogue, an order that can involve two sellers at once. The hard part is not the catalogue, it is what happens after the order.
Portal and customer area
Your customers follow their own files, upload documents and see where their request stands instead of calling you. The gain is measured in calls you no longer take.
Software sold by usage
One product used by several client companies, each seeing only its own data. Data separation is the main constraint here, ahead of any feature.
Booking and appointments
Slots, limited resources, cancellations. Two people must never be able to book the same slot, and that single rule shapes the architecture.
Matching and introductions
A request on one side, providers on the other. Quality is decided by how profiles are verified and by what happens when the relationship goes wrong.
Internal operations platform
A tool your team and your partners use to work: tracking files, deliveries or field jobs, with roles and a trace of every decision.
3. The situations that make a founder call us
We rarely meet a complete written specification. These are the usual starting points:
4. The first version, and what it really contains
A platform that waits until it is complete before going online learns nothing from its users and costs everything before returning anything. We build the shortest version that lets a real user get all the way through the main journey. The pieces below are the ones that make up that first version almost every time.
Accounts, roles and permissions
Sign-up, sign-in, password recovery, and above all the boundary between what each role can see and do. It is written first and compromised on last.
The main journey, end to end
One journey, but complete from start to finish. A platform with three half-built journeys cannot be tested; a platform with one working journey can be tested on day one.
The administration area
You must be able to correct, suspend, refund and reply without calling us. A platform with no admin turns every incident into a billable request.
Notifications and messages
Who is told what, through which channel, and what happens when the message does not arrive. Email templates are written in the languages your users read.
Search and navigation
Finding the right listing, file or record. In Arabic that requires specific handling, because a naive search does not find what the user typed.
Languages and reading direction
French, Arabic and English if your audience needs them, with a genuine right-to-left layout for Arabic rather than translated labels on a left-to-right page.
What is not in the first version is not abandoned: it goes into a dated list, with the reason it is waiting. A written list can be discussed; a verbal promise can only be disputed.
Describe your platform projectAn idea in three sentences is enough to start. The quote follows the scoping, never the other way round.Describe my project5. What has to be settled before any code
The decisions below cost a conversation before development and cost a rewrite after it. They are made at scoping, with you, and they are written into the specification. In Algeria the heaviest of the five is payment.
1. Who pays whom, and when
Online card payment in Algeria runs through SATIM, for CIB and EDAHABIA cards, and requires a contract with your own bank plus an approval that belongs neither to you nor to us. It is not a checkbox. We tell you what the process involves and when to start it, and we will not describe any payment integration as done before your bank file exists. Many platforms start on cash on delivery or offline payment, deliberately and by design.
2. Who owns the data
What your users upload, what you may do with it, what you must be able to delete and what you must keep. This is written first, because it shapes the database.
3. What is checked, and by whom
A listing, a profile, an uploaded document. Moderation is a product decision before it is a feature: automatic or human, before or after publication, each with a different running cost.
4. What happens when it goes wrong
A cancellation, a dispute, a refund, a user to suspend. A platform is judged on those cases, because they are the ones the founder personally handles in the first months.
5. What the platform does if it works
We do not optimise for traffic you do not have. But we avoid the choices that would make growth impossible without a rewrite, and we tell you which ones we avoided and why.
If a provider presents card payment as a simple checkbox, ask them to show you the bank contract that goes with it. That document, not the code, is what governs the schedule.
Does what you describe sound more like an internal tool?
If the users are your own teams and the subject is stock, purchasing or invoicing, a public platform is not what you need.
See the management software and ERP page6. How a project runs
The sequence does not change with the size of the project. It is built so you can stop at the end of any stage with something usable in your hands.
1. Product scoping
We write down who the users are, what each of them comes to do, and the main journey from start to finish. We also list what will not be in the first version, which is often the most useful part of the conversation.
2. Written specification you validate
You receive the first version described in plain language: screens, roles, rules, error cases and limits. The quote covers that document. You validate it before any code.
3. Development in visible iterations
The platform is online on a test address within days and you watch it grow. You can click it, break it, come back to us, and a correction asked for now costs a fraction of the same correction after launch.
4. Acceptance with real users
We put real people through the journey, on phones and on an average connection, before anyone talks about launching. What they do not understand gets fixed, not explained.
5. Go-live and handover
Production deployment, transfer of hosting and domain accounts into your name, handover of the code and documentation, and training for whoever will administer the platform day to day.
7. What happens after launch
Launch is not the end of the project, it is the moment the platform finally starts teaching you something. What comes next is decided at that point and contracted separately, never by silent renewal.
- The first corrections come from users and not from the specification. That is normal and it is planned for.
- The second version is decided on what people actually do, not on the list written six months earlier.
- Maintenance, security updates and hosting are a separate agreement, with what it covers written down.
- You can continue with another team: that is exactly what the handed-over code and documentation are for.
- We tell you what we will not be able to do, when that is the case, rather than learning at your expense.
What you own at the end
- The complete source code, in a repository you have access to.
- The domain name and hosting accounts, in your name and not in ours.
- The database, exportable in an open format at any time.
- The technical documentation and a guide to the administration area.
8. What you can open and check yourself
We publish no testimonial, no rating and no project figures. The clients we are free to name are named on our portfolio page, each with the address of their site. Instead, the site you are reading is itself a platform we built, and you can open every part of it right now. It is fully pre-rendered to HTML, served in three languages including a right-to-left edition, and it carries its own search engines and its own calculators.
All of it is open and requires no account. Open it, type in it, try to break it. That is a check we far prefer to a brochure.
See everything we have built9. What to prepare before writing to us
You do not need a written specification. You need answers to these questions, even approximate ones.
- Who your users are, and how many different types of them there are.
- What the most important of them does, from the first screen to the end of their journey.
- How this happens today without a platform, including if it is by phone and in a spreadsheet.
- If money moves, between whom and whom, and at what moment.
- The languages your users read, and whether Arabic is one of them.
- What already exists: a mockup, code from a previous provider, a domain name, accounts.
- What drives your schedule: a panel, a partner, a season, a financing deadline.
10. Frequent questions
How much does a web platform cost in Algeria?
From 500,000 DA for a first version in service: written scoping, data model, accounts and permissions, the screens of the main journey, a dashboard, and deployment on hosting in your name. A platform differs from a site by what it lets users do, not by page count, and it is that set of actions that sets the price. The firm quote comes after scoping, on a specification you have approved.
How long does it take to build a web platform?
A web platform is delivered within four weeks, a maximum for the scope described in our price table. The firm schedule is part of the specification: it is set with you and its assumptions are written down, because a schedule announced without a scope is a sales promise and not an estimate. On a very specific development the time has no ceiling.
Can you integrate CIB or EDAHABIA card payment?
Card payment in Algeria runs through SATIM and requires a contract between your company and its bank, then an approval that does not depend on us. So we describe no integration as done while that file does not exist. What we do is tell you what the process involves, when to start it, and design the platform to work without it in the meantime.
Can you take over a web platform another provider started?
We look at what exists before proposing anything, and we tell you plainly whether taking it over costs more than rewriting. Both answers happen, and honesty on that point is the only thing protecting you from a second failure.
Who owns the code at the end?
You do. The code repository, the database, the domain name and the hosting accounts are in your name. We hand them over at go-live and not at the end of a maintenance contract, because a company that cannot leave is not a client.
Do we also need a mobile app?
Not necessarily, and rarely first. A well-built web platform works on a phone. An app earns its place when you need push notifications, offline use or the camera. That decision belongs after the first launch, with real users as the argument.
Can we have a web platform in Arabic?
Yes, with a right-to-left layout, a search that accounts for spelling variants, and local date formats, not only translated labels. The site you are reading serves its three languages that way and you can check it at the top of this page.
Can you help us apply for the startup label or for financing?
That is a different trade from development and we do not mix the two in one quote. We document those schemes publicly and you can consult them freely on this site. On the product side, our job is to make the thing you will be showing exist.
Let us talk about the first version of your platform
Write to us through the form, on WhatsApp or by e-mail. Three sentences are enough to start. We scope the main journey, then propose a written scope and a quote that covers it.
