Services — Cloud Mist Labs

Services · v1.0 · 2026
The whole list of what we’ll do for you.

The procurement-friendly version of Practice. Capabilities, engagement shapes, the stack, and what we explicitly don’t do. Read it; pick a starting point; book a call.

Founded
2026 · Dubai
Strata
Edge · Services · Data
Team
3 principals
Pricing
Retainer + fixed-fee shapes
Availability
Q3 2026
· 01 · how we work

Four shapes.

Most engagements fit one of these. We’ll tell you which on the first call.

· 01 · Discovery 2 weeks · fixed fee

A scoping engagement. We read the system, talk to the team, and deliver a written plan with options, risks, and a calendar.

  • Written architectural review
  • Three-option plan with calendar
  • Signed risk register
You have an idea of what to build but need a sober plan before committing to the build.
· 02 · Full Build 3 – 18 months · monthly retainer

The main engagement. We design, build, and ship the system end-to-end across Edge, Services, and Data. Monthly signed checkpoints. Weekly written status. No surprises.

  • Working software, in production
  • Monthly signed checkpoint document
  • Final handoff doc the team owns
You have a project to ship — a new system, a rebuild, an AI integration — and you want one team end to end.
· 03 · Advisory Quarterly retainer

Eight hours a month. We read your PRs, sit in on architecture reviews, and write a monthly note on what we see drifting.

  • Monthly written note
  • On-call architecture review
  • Quarterly deep-dive doc
You have an internal team and want a sober second pair of eyes on the next twelve months.
· 04 · AI Readiness 4 weeks · fixed fee

A pointed look at where AI and agents fit (and where they don’t) in your existing systems. A written report a board can read. Heavy on specifics, light on hype.

  • Findings report with line-item evidence
  • Prioritised opportunities + risk register
  • One-page summary for stakeholders
You’re being asked “what’s our AI strategy” and need an honest, ungimmicked answer.
See our field note on AI in the region
· 02 · the matrix

Three strata. Fifteen capabilities.

Each row is one engagement-shaped chunk of work. Pick rows — not strata — when you book.

See in practice
· 01 · Edge

design systems · web · mobile · brand

  • Design systems

    Components, tokens, documentation. Built to outlast a redesign.

  • Interface design

    Web and mobile screens. Wireframe → high-fidelity → engineered handoff.

  • Mobile development

    iOS and Android. Native where it matters, cross-platform where it doesn’t.

  • Brand identity

    Logo, marks, voice, type, photography direction.

  • Accessibility

    WCAG 2.2 audits, remediation, documentation.

· 02 · Services

APIs · integrations · databases · infra

  • API design

    REST or GraphQL, versioned, documented, signed at the boundary.

  • System integrations

    Payment, CRM, ERP, government services, third-party APIs.

  • Database design

    Schemas, migrations, indexes. Built to grow without breaking.

  • Infrastructure

    Deployment, observability, cost discipline. Boring on purpose.

  • Authentication

    Identity, access control, session safety. One auth surface, not three.

· 03 · Data

AI agents · LLMs · analytics · pipelines

  • AI agent development

    Custom agents and copilots that fit inside your existing systems. Tools, not chatbots.

  • LLM integration

    Add language models to existing flows. Right model, controlled costs, measurable wins.

  • Analytics

    Dashboards the business will actually use. Numbers a non-engineer can trust.

  • Data pipelines

    Move data from where it lives to where decisions get made. Reliable, observable, owned.

  • Evaluation

    Tests, metrics, regression detection for AI systems. Specific to your domain.

· 03 · the stack

What we reach for first.

Not the only things we use, but the defaults. If yours differs we’ll match it; we don’t enforce a stack.

Languages
TypeScriptPythonSwiftKotlinSQL
Frontend & web
NextReactTailwindAstroVite
Mobile
Swift / SwiftUIKotlinReact NativeFlutter
Backend
NodeFastAPIOpenAPIRESTGraphQL
AI / agents
OpenAIAnthropicLangChainHugging Facevector DBs (Pinecone, Qdrant)
Data
PostgresSupabaseBigQuerydbtRedis
Infra
CloudflareAWSGCPVercelTerraform
Observability
OpenTelemetrySentryDatadog
Tooling
GitHubFigmaLinearNotion
· 04 · the limit

What we won’t do.

A short list, written down. The thing we don’t want is for a partner to find out three months in.

  • 01

    Staff augmentation

    We work as a team or not at all. Embedded contractors aren’t the practice.

  • 02

    Pure marketing or SEO sites

    We build sites when they’re attached to a product engagement. Standalone, we’ll refer.

  • 03

    Crypto, blockchain, web3

    Unless specifically scoped against a real, legal use case. Defaults are off.

  • 04

    Anything before discovery

    No fixed-bid builds without a two-week Discovery first. No exceptions.

· 05 · process

From the first call to the last commit.

Five steps. Each one has a document. Each document is signed.

  1. 01

    Intro call

    30 min

    Thirty minutes. We talk about the system, you ask whatever you want. No pitch deck.

  2. 02

    Written proposal

    5 business days

    A two-page document describing scope, calendar, and price. Signed.

  3. 03

    Discovery

    2 weeks

    A two-week scoping engagement. We deliver a plan that becomes the build SOW.

  4. 04

    Build

    3 – 18 months

    End-to-end across Edge, Services, and Data. Monthly signed checkpoints. Weekly written status.

  5. 05

    Handoff

    + 60 day grace

    A document the team can own. We stay reachable for sixty days, no clock.

· 06 · at a glance

Capabilities, scope, fit.

One table. Print it. Bring it to the call.

Stratum Capability Fit Typical scope Start with
StratumEdge CapabilityDesign system Fit● Best Typical scope1 – 3 months Start withDiscovery
StratumEdge CapabilityWeb app build Fit● Best Typical scope3 – 9 months Start withDiscovery → Build
StratumEdge CapabilityMobile app Fit● Best Typical scope4 – 10 months Start withDiscovery → Build
StratumEdge CapabilityBrand identity Fit● Best Typical scope2 – 4 months Start withDiscovery → Build
StratumEdge CapabilityAccessibility Fit○ Good Typical scope3 – 5 weeks Start withDiscovery
StratumServices CapabilityAPI design Fit● Best Typical scope2 – 5 months Start withBuild
StratumServices CapabilitySystem integrations Fit● Best Typical scope1 – 6 months Start withBuild
StratumServices CapabilityDatabase design Fit● Best Typical scope2 – 5 months Start withDiscovery → Build
StratumServices CapabilityInfrastructure Fit○ Good Typical scope1 – 3 months Start withAdvisory
StratumData CapabilityAI agent development Fit● Best Typical scope2 – 6 months Start withAI Readiness → Build
StratumData CapabilityLLM integration Fit● Best Typical scope1 – 4 months Start withAI Readiness → Build
StratumData CapabilityAnalytics Fit○ Good Typical scope2 – 4 months Start withBuild
StratumData CapabilityData pipelines Fit○ Good Typical scope1 – 3 months Start withBuild
StratumData CapabilityEvaluation Fit● Best Typical scope2 – 4 weeks Start withAI Readiness
StratumCross-cutting CapabilityAdvisory retainer Fit● Best Typical scopeOngoing Start withAdvisory

● Best — we do this all the time · ○ Good — we do this when it sits inside a build

· 07 · how to start

Pick a row. Book a call.

We answer within two business days. The first call is thirty minutes, free, no slides. If we’re not a fit, we’ll say so and recommend two firms that are.

Currently
Booking
Q3 2026
Response time
≤ 2 business days
Minimum engagement
Discovery (2 weeks)
Mhd Ghaith Al Abtah
Founder · 2026