Process
How a project actually runs.
Most of what goes wrong in software projects is decided before any code is written — in how the scope was agreed and how the price was set. So that is where we spend the most care.
From first call to handover
Eight steps, with the price fixed at step two.
-
1
Call
Twenty to thirty minutes. What you need, who it is for, what it has to do, and when. If we are not the right fit we will say so on this call.
-
2
Written scope and fixed price
You receive a document listing exactly what will be built, what it costs, and when it will be delivered. One number, not a range.
-
3
Deposit and start date
A 50% deposit books the slot. Accounts are created in your name at this point, not at the end.
-
4
Design
You see and approve the design before anything is built. 2 rounds of revisions are included.
-
5
Build
You get access to a staging site from the first week and can watch it come together. No disappearing for two months.
-
6
Review and launch
You test it against the written scope. We fix what does not match, then go live at a time that suits you.
-
7
Handover
Code, accounts, documentation and a walkthrough with whoever will be running it.
-
8
After launch
30 days of bug fixing included. A care plan if you want us to keep looking after it — and no hard feelings if you do not.
What you own at the end
Everything below is yours, transferred to you, on every project. This is not a premium tier.
- The source code
- In a repository you own, with the history intact. You can hand it to any developer and they can continue.
- Every account, in your name
- Hosting, domain, database, payment provider, email. Created as yours from the beginning, never transferred out of ours later.
- Documentation a developer can use
- How it is structured, how to run it locally, how to deploy it, and what depends on what.
- An editing guide for your team
- Written for the person who updates the content, not for an engineer.
- Design files
- The full design source, plus the component library if we built one.
- Backups and a restore that has been tested
- Automated, encrypted, and proven to restore before we consider the project delivered.
- 30 days of bug fixing
- If something we built is broken after launch, we fix it. That is not billable work and it is not a support plan.
No lock-in. If you leave, you lose nothing but us.
Standards we build to
We build to published standards rather than to house habit, because it means the next developer to touch your system already knows the conventions.
| Standard | Applied to |
|---|---|
| WCAG 2.2 AA | Accessibility, on every build |
| Core Web Vitals | Performance targets we measure against |
| OWASP ASVS | Application security requirements |
| Schema.org | Structured data for search and AI assistants |
| WAI-ARIA | Assistive technology support |
| PCI DSS SAQ-A | Payment integration that keeps card data off your servers |
| Semantic versioning | Dependency and release management |
| Conventional commits | Readable history for whoever comes next |
What we will not do
- Start building before the scope is written down and agreed.
- Register your domain, hosting or payment accounts in our own name.
- Bill you hourly for a scope we quoted as a fixed price.
- Hand over a system with no documentation and no way to run it.
- Add analytics or tracking to your site without telling you what it collects.
- Take on work we do not think we are the right people for.
Contact
Tell us what you are trying to build.
A short call is usually enough to give you a clear scope, a timeline and a fixed price. If we are not the right people for it, we will tell you on that call.
fadi@fd-sol.com +20 106 869 4544
Every account we create is registered in your name, and the source code is yours. There is no version of working with us that leaves you dependent on us.