Mobile speed target
< 2.5s
Largest Contentful Paint on mobile — the target we build every page to, as published on our standards page.
Next.js · Right-to-left included
Custom website development.
Custom website development on Next.js: sites that explain what you sell, help customers find you and make it easy to get in touch, in a typed codebase you own. Internal systems and workflow tools are custom software.
Websites, managed content, forms and integrations, handed over with the code and documentation.
What each one includes
Four parts of a website, built the same way.
Each one is scoped from your requirements and built on Next.js, in a typed codebase that ends up in your repository. Internal applications, workflow tools and portals are covered by Custom Software.
Websites
Sites that explain what you sell.
- Every language in one codebase, with right-to-left done properly
- Page structures built around what a customer needs to decide
- Speed, accessibility and search targets written into the scope
Content you manage
Pages and posts you edit yourself.
- A content management system, when the scope includes one
- Editing set up for the people who will do it
- Routine changes published without a developer
Contact and enquiries
How customers reach you.
- Contact, quote or booking forms, depending on what you need
- Each enquiry sent to the person who handles it
- Input validated before anything is sent
Integrations
Connected to what you already use.
- Payment gateways, CRMs, analytics and third-party APIs
- Local payment and logistics providers, scoped in discovery
- Each integration reviewed during scoping before it is priced
Who it is for
For work a template cannot hold.
Custom development makes sense when your workflows, roles or data are the product. When they are not, a template is the cheaper path.
A fit when
Your rules are what the system has to carry.
- Your website is where customers judge the business, find what it sells and get in touch.
- You need pages, content and forms shaped around what you sell, not around a theme.
- You want to own the code, the schema and the accounts instead of renting a platform.
- Every language, right-to-left included, has to work properly in one release.
Not a fit when
A simpler path already fits.
- An internal system, workflow tool or portal. That is custom software.
- A straightforward store or blog that Shopify or WordPress already handles well.
- A system that already exists and the right path is unclear. Start with the technical audit.
- Open-ended hourly work with no written scope. Every build starts with a proposal.
What it costs
Custom development · Published range by project type and complexity; fixed in the proposal
From 22,000 EGP
Estimate your projectHow it runs
Five phases, each one signed off.
Delivery runs 2–8 weeks depending on scope. The phase lengths below come from that window; your proposal fixes the dates.
- 01 — Discovery1 session
The initial project consultation call covers the goal, the constraints and what exists today. The proposal that follows sets scope, price and timeline.
Your part: Share the context, and who will use the system.
- 02 — Wireframe2 – 5 days
The sitemap, page structure and key flows. For an application, the roles and what each one can do.
Your part: Approve the structure.
- 03 — Design2 – 7 days
The interface on that structure, with 3 included revision rounds.
Your part: Approve the design. Development starts after your approval.
- 04 — Development3 – 22 days
Built on a live preview link you can open at any time. The milestone payment falls at the point named in your proposal.
Your part: Review the preview and send feedback as you go.
- 05 — Launch2 – 5 days
Hosting set up, a production deploy, and the source code and documentation handed over.
Your part: Approve the launch. The final payment is due before production launch, and ownership passes to you at that payment.
What you receive
What you get, and what moves the price.
Handover
Everything needed to run it without us.
- The source code, in your repository
- The database schema and its migrations
- An environment and secrets guide
- Deployment documentation
Price and time
Set by scope, complexity and readiness.
- The pages, screens and features in scope
- Complexity: roles, workflows, data and integrations
- Whether content and brand assets are ready
- The timeline you need: an urgent date moves the price
What you provide
Access, content and one decision-maker.
- Access to the systems the build has to connect to
- Content and brand assets, or a decision on who will produce them
- Someone who can answer questions and approve each phase
- Domain and hosting accounts in your name, or set up by us and passed to you
After launch
Covered, then yours to decide.
- A 30-day warranty covering critical fixes
- Then a maintenance plan, changes quoted as needed, or your own team
- Another developer can take over; the handover is written for that
How we build
We plan the data, roles and screens before writing code, so the next developer, yours or ours, can read it, change it and own it.
What every build is built to
Published targets you can check yourself after launch.
Ownership
100%
Of the custom source code, schema and documentation, in your repository and yours at the final payment.
Languages
2
Every language in one codebase and one release — never a translated afterthought.
Templates suit specific cases, such as Shopify for a straightforward store or WordPress for a blog. When a business has its own workflows, local payment methods or roles that do not fit a plugin, the template becomes the limit. A custom build is designed around those rules and stays yours.
Delivery runs 2–8 weeks depending on scope and complexity. The estimator gives an indicative range, and your proposal sets the delivery window once the scope is agreed.
Next.js, in a typed codebase, deployed on Vercel or on your own infrastructure. Every language lives in one codebase with right-to-left layout built in.
Yes. The source code, database schema and documentation are handed over in your repository, and code, designs and accounts pass to you at the final payment. There is no licence fee and no lock-in.
The published range depends on project type and complexity, and the price is fixed in the proposal. Payment is split 50% to start, 30% at a development milestone, and 20% before production launch.
A 30-day warranty covers critical fixes. After that, you choose a maintenance plan, pay for changes as needed, or hand the system to your own team with the documentation it needs.
Next step
Describe the website you need built.
Tell us what it has to do, who it is for and what it replaces. We reply with the next step.