Services
Outsource the technical work. Keep your time for the market.
You know the customer, the market and the idea. We supply the entire technical side as a fixed-scope engagement: product, architecture, security, infrastructure and launch. The output is a working product you own and can run, not a deck.
Who this is for
- Non-technical founders with a validated problem and a budget, who would rather test the market than recruit and manage engineers.
- Operators adding a digital product to an existing business, where reliability and security matter more than novelty.
- Agencies and consultancies that need a product built for a client and want a build team that ships without hand-holding.
Who it is not for
Teams that want to hire an engineering department by the hour, or projects where the scope cannot be fixed. We work on defined deliverables so that both sides know what "done" means.
What is included
- Product Scoping, information architecture, bilingual-ready UI where needed, and working software from the first week.
- Architecture A stack chosen for the scale you will actually reach, documented so that any competent team can take it over.
- Security Threat model, hardening pass and a written security review before launch. Encryption, access control and audit logging are part of the build, not an add-on.
- Infrastructure Containerised deployment, backups with restore tests, monitoring and alerting, hosted where your data needs to live.
- Launch Domain, edge protection, app-store or web release, and a handover pack.
Packages
Fixed scope, fixed price, agreed before we start
Every engagement is quoted after a short scoping exchange. We do not publish a price list, because the same package costs different amounts depending on integrations, languages and compliance needs. Quotes are itemised so you can see what drives them.
Validate
Prototype
Typically one to two weeks
A working, data-backed prototype you can put in front of real users and investors. Not a mock-up: real screens, real flows, real data where it matters.
- Scoping and product definition
- Clickable product on a private staging URL
- Bilingual UI where the market needs it
- Feedback capture built into the prototype
- Written recommendation for the production build
Launch
Production build
Typically four to eight weeks
The full product, built to run: application, architecture, security hardening, infrastructure, monitoring, backups and launch.
- Everything in Prototype
- Production architecture and data model
- Threat model and written security review with fixes
- Containerised deployment, backups with restore test, monitoring
- Launch on your domain, app stores where applicable
- Documentation and handover runbook
Run
Retainer and hosting
Monthly, three tiers
After launch: Support, Standard or Priority retainers priced as a percentage of project value, and managed hosting with a 99.5% uptime commitment. The first three months of Support are included with every build.
- Support: bug fixes only
- Standard: plus minor changes within scope, 7-day SLA
- Priority: 3-day SLA
- Managed hosting add-on with service credits
Every build is paid in six stages as fixed percentages of the quote, starting with 10% for a scoping document and a working proof of concept. After launch, three stacking retainer tiers and managed hosting are priced as a percentage of project value. All of it is public on the How we work page.
Why weeks, not months
How a small team ships this fast
Three things, none of them magic. A small senior team with no hand-offs between "product", "engineering" and "security". A hardened platform of components we have shipped before: authentication, bilingual right-to-left interfaces, admin consoles, containerised deployment, backups and monitoring. And AI-assisted engineering used under senior review, which lets us run several workstreams in parallel and spend our attention on the decisions that matter.
We quote from what our own delivery records show, not from optimism. If a scope will not fit the weeks we have promised, we say so before you sign rather than after.
What you get at the end
- Source code, infrastructure definitions and data, in your accounts where you want them
- Architecture, operations and decisions written down
- A security review with findings and their fixes
- Backups with a restore that has actually been run
- A staging environment and a production environment
- A clear path to keep building: your team, or ours on retainer
Process
What the weeks look like
Week 0: scope
You describe the product and the market. We return a written scope, a fixed price, the stack and the delivery plan.
Weeks 1 to n: build
Working increments every week on a private staging URL. Feedback is captured in the product itself, so nothing gets lost in chat threads.
Before launch: harden
Security review with findings and fixes, backup restore test, monitoring, documentation and a runbook.
Launch and handover
Go-live on your domain and infrastructure. Then either a clean handover to your team, or a monthly retainer with us.
Capabilities
What we build
Consumer platforms
Marketplaces, directories, booking and matching products, on the web and on iOS and Android. Bilingual and right-to-left where the market needs it, from the first screen rather than as a retrofit.
Operational software
Admin consoles, back-office tools, dashboards and reporting built on your own data, for teams that have outgrown spreadsheets and shared inboxes.
Data, AI and security
Search and matching, document analysis, assistants grounded in your own data, and the access control, isolation and review that have to come with them.
If your product does not sit neatly in one of these, describe it on the contact page. We will tell you plainly whether it is work we can do well.
Questions founders ask
Do you publish prices?
Our commercial model is public: the payment ladder, the retainer tiers and managed hosting are all on one page. The total for a build depends on the scope, so it is quoted; the estimator gives you an indicative range in five minutes and the written scoping document confirms it.
Who owns the result?
Ownership of code, data and infrastructure is set out in the statement of work before the build starts. You will never be locked into hosting with us.
Can you build in Arabic or French?
Yes. Right-to-left Arabic, French and English interfaces are standard in our work, including bilingual content generated in one pass.
What if we need more after launch?
The monthly development retainer gives you a fixed allocation of the same team. You set the priorities each month.
Can our data stay in-country?
Yes. We deploy on infrastructure in the jurisdiction you need, including self-hosted stacks with no mandatory third-party services on the core path.