What Does a Web Development Company Actually Deliver? Code, Hosting and Handover: the Full List
Working software is only part of it. A web development company should also hand over the source code, the accounts, a test environment, documentation and a way to maintain it. Here is the full list, phase by phase.
A web development company delivers a working website or app, the source code behind it, the environments it runs on, and the documentation and access you need to run it without them. In practice that means: a technical plan, a code repository, a test version, the live product, an admin panel, basic SEO and analytics setup, and a handover of every account. By the end you should own the code and control the domain and hosting.
Here is the full list by phase, so you can check any proposal against it.
What are the deliverables at each phase?
| Phase | Deliverables | Why it matters |
|---|---|---|
| Discovery | Feature list, technical plan, choice of technology, timeline and milestones | Everyone agrees what is being built before code is written |
| Setup | Code repository, a test (staging) environment, automatic deployment | You can see progress on a real link, not in screenshots |
| Front end | Every page and screen built from the design, responsive, in each language | What users see and touch |
| Back end | Database, user accounts, business logic, admin panel | What makes the product work |
| Integrations | Payments, maps, SMS or email, analytics, any external system | Connects the product to the tools your business already uses |
| Quality | Testing on real devices and browsers, bug fixing, speed and security checks | Problems are found before your customers find them |
| Launch | Live deployment, domain and SSL, redirects from the old site, backups | The moment it goes public, done without losing traffic |
| Handover | Source code, access to all accounts, documentation, admin training | You are not locked in to the company that built it |
| After launch | A warranty period for bugs, then an optional maintenance plan | Software needs updates; agree who does them |
A small landing page will not need every row. A web app, a platform or a mobile app should include almost all of them.
What should you own at the end?
- The source code, in a repository under your account or transferred to it
- The domain name, registered in your name
- The hosting or cloud account, in your name, with the developer added as a user
- Accounts for every service used: payment gateway, email, maps, analytics, app stores
- The database and its backups
- Design files, if the same company did the design
- Documentation: how to run the project, how to deploy it, and how the main parts work
Ask one question before you sign: "If we stop working together, can another developer take over in a week?" If the answer is not a clear yes, the handover is incomplete.
What is often missing?
- A staging environment. Without one, changes are tested on the live site.
- Admin training. Your team gets a panel and no explanation.
- Redirects from the old website. Old links break and search traffic drops.
- Analytics and search setup. Nobody can tell whether the launch worked.
- Backups. They exist only after the first incident.
- Empty, loading and error states. The product works only when everything goes right.
- A plan for updates. Frameworks and libraries need updating; if nobody owns that, the product ages quickly.
Development company, freelancer or in-house team?
| Best for | Watch for | |
|---|---|---|
| Freelancer | Small, well-defined tasks | One person: no cover for illness, limited range of skills |
| Development company | A full product with design, build, testing and launch | Make sure the people in the pitch are the people doing the work |
| In-house team | A product that is your core business and changes every week | Hiring time and fixed monthly cost |
If you run a software house and need extra capacity instead of a full project, see staff augmentation for software houses.
How do you check a proposal?
1. Does it list what you will own at the end? 2. Does it include a staging link you can open during the project? 3. Are testing and launch separate line items, or assumed? 4. Is there a warranty period for bugs after launch, and how long? 5. Is the technology named, with a reason for choosing it? See what a tech stack is and how to choose one. 6. Is the pricing model clear? See fixed price vs time and materials vs retainer.
What Flowlix delivers
Flowlix Studio is a design and development studio in Ismailia, Egypt. We design the product and build it in one team: websites and web apps in React and Next.js, mobile apps in Flutter and React Native, plus brand identity and e-commerce stores. On a development project you get a staging link to follow progress, the source code in your repository, the accounts in your name, and a documented handover. We work with clients in Egypt, Saudi Arabia, the UAE and Qatar. More on our web and app development service.
Frequently asked questions
Who owns the source code after the project?
You should. Put it in the contract: full ownership of the code transfers to you on final payment. Third-party libraries keep their own licences, which is normal.
Is hosting included in the price?
Usually not. Hosting is a running cost paid to a cloud provider, monthly or yearly. The company sets it up; you pay the provider directly so the account stays yours.
What is the difference between front end and back end?
The front end is what people see and interact with in the browser or app. The back end is the server, database and logic behind it. Most products need both.
What happens if I find a bug after launch?
A good contract includes a warranty period in which bugs in the delivered scope are fixed at no cost. New features and changes are separate work.
Talk to us
Book a free consultation on WhatsApp. We will send a scope that lists every deliverable, what you will own, a timeline and a fixed quote within 48 hours.