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

Every project runs on the same weekly rhythm: a demo you can click every Thursday and a written update every Friday. You'll always know what shipped, what's next and what's at risk.

A week in a project · UAE working week

  1. MondayPlan

    Agree the week's goals on the shared board.

  2. TuesdayBuild

    Design and code land in your tools, visible as they happen.

  3. WednesdayCheck-in

    15 minutes on blockers and the decisions you need to make.

  4. ThursdayDemo

    Working software on a link you can click. Not slides.

  5. FridayWritten update

    What shipped, what's next and what's at risk, on one page.

What you get access to on day one

Your repository. Created in your organisation's account, not ours.

The shared board. Every task, its owner and its status.

A staging link. Updated after every merge, so you can try things between demos.

A direct line. A WhatsApp group with the engineers building your product.

Leaving is designed in

Every project ends with a handover: architecture notes, runbooks, a recorded walkthrough, and a session with your team. The goal is that you could run the product without us, even if you choose not to.

To fill · sample weekly update

A real Friday update from a past project, with client details removed.

Next step

An engineer replies within one UAE working day.