Skip to content
Preview.Dashed boxes are slots for real details. Sample findings are illustrative. Prices are starting assumptions. The form sends nothing yet.
Isha Core

One senior team that designs, builds and runs your web, mobile and AI products, from the screen to the server. Published prices, a demo every week, and the engineer you meet is the one who builds it.

A real engineer replies within one UAE working day.

day

Until a real engineer replies. No sales queue.

days

To a full Core Check report on your product

weeks

From kickoff to a fixed build quote

thousand AED

Where our published prices start

01

They're about missed dates, handoffs between vendors and agencies that go quiet. This is what we hear on first calls, and what we do about it.

  1. 01

    “Three months,” they said. It's been nine.

    Our fix ·A fixed quote after a two-week sprint, and a demo every Thursday so slippage shows in days, not quarters.

  2. 02

    Seniors pitched it. Juniors built it.

    Our fix ·The engineer on your first call is named in the proposal and leads the work.

  3. 03

    Design, app and hosting are three vendors blaming each other.

    Our fix ·One team owns all four layers, from the screen to the server. No handoffs to fall between.

  4. 04

    Nobody wants to touch the code anymore.

    Our fix ·A Core Check maps the risks in five working days and ranks every fix by impact and effort.

  5. 05

    The Arabic version looks broken.

    Our fix ·Arabic-first, right-to-left design built into every screen from day one, not translated at the end.

  6. 06

    The AI demo impressed the board, then never shipped.

    Our fix ·AI features in the live product, with your data, guardrails and a real monthly cost.

  7. 07

    You can't get a straight answer on price.

    Our fix ·Our prices are on this site. You get an exact figure before you commit.

Tools we work in: Figma, Next.js, React, Flutter, TypeScript, Tailwind CSS, Go, PostgreSQL, Supabase, LLM APIs, Vercel, Cloudflare, Arabic RTL. How we work: Published prices, Named engineers, A demo every week, Your code, your accounts, One team, no handoffs, No lock-in.

03

From the screens your customers touch to the servers they never see. Bring us the one layer that's hurting, or hand us the whole product.

L1 · FIGMA · NEXT.JS · FLUTTER

Interface

“Users get lost, the app feels slow, and the Arabic version looks broken.”

  • Product design and UX for web and mobile, from user flows to a working design system
  • Web apps in Next.js and mobile apps in Flutter, fast on mid-range phones
  • Arabic-first, right-to-left interfaces built in, not bolted on

L2 · GO · GIN · REST · QUEUES

Logic & APIs

“Checkout times out every time we run a sale.”

  • Backend services and APIs, queues and background jobs that hold up at peak
  • Integrations with payment gateways, ERPs and government platforms
  • Rescues of inherited codebases, left in a state your own team can own

L3 · POSTGRES · PIPELINES · LLM

Data & AI

“Our reports lock the database, and the AI pilot never shipped.”

  • Database design, migrations, pipelines and reporting that doesn't slow the product
  • AI features in live products: retrieval, guardrails, evaluation and cost control
  • Data residency designed in for UAE and Saudi users

L4 · CLOUD · CI · OBSERVABILITY

Infrastructure

“Deploys are scary and nobody knows why the app is slow.”

  • Cloud setup, automated deploys, monitoring and alerting
  • Hosting regions chosen with you and stated in writing
  • Runbooks and a real handover, so you're never dependent on us

04

Not sure what's wrong with your product? A Core Check tells you, in writing, in five working days. This is what the report looks like. The findings are illustrative, written to show the format, not taken from a client.

CORE CHECK · REPORT
Sample · illustrative findings

Risk map

Findings placed on the layer where they live.

3 High3 Medium1 Low

Also in the report

  • UX review of your key flows
  • Architecture notes and a diagram
  • Hosting and data-region review
  • 60-minute readout with your team

Fix order

  1. A retried webhook from the payment gateway can create a second order for the same payment.

    Fix · Store the gateway event ID and ignore repeats. About a day of work.

    Layer L2Effort Small

Showing Payment callbacks can double-charge

Five working days, a fixed fee, and a report your team can act on, with or without us.

05

A small senior team is right for some projects and wrong for others. If we're not right for yours, we'll say so on the first call and suggest who might be.

A good fit if

  • Yes:You've been burned by an agency that missed dates or went quiet
  • Yes:You want one team accountable for design, build and hosting, not four vendors
  • Yes:Your product is growing and the cracks are starting to show
  • Yes:You need English and Arabic, and UAE or Saudi data rules, done right from day one

Not the right team if

  • No:You need the lowest price per hour, whoever does the work
  • No:You want a clone of an existing app from a template
  • No:You need a logo, brand identity or ad campaign
  • No:You need a team of 30 by next month

06

No six-week proposal process and no big upfront bet. A short, fixed-price first step tells both of us whether to go further.

  1. STEP 01

    A straight conversation

    30 minutes · free

    You talk to the engineer who would lead your project, not a salesperson. If we're the wrong fit, we'll say so.

  2. STEP 02

    Sprint or Core Check

    1 to 2 weeks · fixed fee

    A prototype or an audit report, plus a fixed quote for what comes next. No six-week proposal process.

  3. STEP 03

    Build, in the open

    Fixed-scope phases or a monthly team

    A demo every Thursday, a written update every Friday, and your code in your accounts from day one.

Next step

An engineer replies within one UAE working day.