What we build

What you get

• Arabic and English from the first commit, with right-to-left layout that is designed, not mirrored.

• Customer accounts, role-based admin and the records behind them, on PostgreSQL.

• Transactional email, PDF documents and payment or booking flows wired end to end.

• Static where it can be, server-rendered where it must be, so pages load fast on mobile data.

• Deployed with a rollback path, monitored, and handed over with the source and a runbook.

Typical scope

A company site in four to six weeks. A platform with accounts and admin in two to three months.

Stack

• Next.js
• React
• TypeScript
• Tailwind
• Prisma
• PostgreSQL
• NextAuth
• next-intl

What you get

• Android and iOS from one codebase, so features ship to both stores on the same day.

• Store listings, signing, review and release handled, not left to you.

• Arabic and English in the app, with right-to-left screens tested on real devices.

• Offline-tolerant where the use case needs it, with sync against the same API as the web.

• Release notes and versioning, so you know what changed and when.

Typical scope

A first release in two to three months, depending on the number of screens and the API work.

Stack

• Flutter
• Dart
• Google Play
• App Store

What you get

• WhatsApp connected to an agent that reads, answers and hands over to a person when it should.

• CRM automations: enrich, route and follow up without a person copying data between tabs.

• MCP servers that give an agent safe, scoped access to your own systems.

• Built on the Claude API, with every action logged and reversible.

• Scoped to one workflow first, measured, then widened.

Typical scope

A first workflow in two to four weeks, inside an existing platform or as its own service.

Stack

• Claude API
• MCP
• WhatsApp Business API
• Node.js