Hai. hi + AI — Appaya Ltd

Audit, lead, or build.

Appaya is the London studio of Luke Czak — fractional CTO and hands-on engineer, previously Global Head of Technical Product Management at HSBC, and a product leader at Zopa, Smarkets and Shieldpay. A fixed-fee audit of what you have built, then ongoing technical judgement once you know.

Appaya is an AI-native studio with three productised offers, not a generic agency menu. A human directs a fleet of AI engines that build in parallel, and every change is proven before it reaches you.

Orchestrates Claude · Codex · Gemini · + whichever engine earns the job

13 years in product & engineering HSBC · Zopa · Smarkets · Shieldpay every change cross-reviewed by a second engine prices published, not quoted after a call 1 correction round on every offer findings shown, never asserted
We seed software. proof over promises throughput of many, judgment of one taste is a feature order from many elements proven before it reaches you

01 — How we work together

Decide, lead, or build.

Most clients start with a decision. Some stay there. Others move to ongoing leadership, then to delivery — start wherever fits today.

Audit

AI Codebase Audit

You built it with AI and it works. Find out what is actually underneath it before real users arrive.

  • Repository, architecture & security
  • Retain, improve or rebuild — stated plainly
  • A prioritised 60–90 day plan

Timing Delivered in 5 working days.

Fixed fee, quoted at a fit check

Good fit when you have shipped something with Claude Code, Lovable or Cursor and need an honest read on it.

See the Audit
Lead

Fractional technology leadership

Ongoing senior technical leadership — technical direction, architecture, hiring, and delivery discipline, without a full-time hire.

  • Two to four days a month
  • Owns technical direction & the board relationship
  • Reviewed quarterly, never locked in for a year

Timing 3-month minimum, reviewed quarterly.

Monthly retainer, set at a fit check

Good fit when you have engineers but no senior technical head accountable for the calls.

See Fractional
Build

Fixed-Scope Build Sprint

Production software built by human-directed AI agent fleets, shipped with real cross-engine review rigor.

  • One engine builds, a different engine attacks the diff
  • Proof-of-work gates, anti-fabrication checks
  • Fixed scope, fixed fee, per engagement

Timing Set per engagement, once scope is locked.

Fixed scope, fixed fee per engagement

Good fit when you have one bounded outcome to ship and are out of engineering capacity.

Start a build

02 — Data & confidentiality

What we handle,
and what we don't.

The public enquiry below is not the place for anything sensitive — here's the boundary, plainly.

01

What you can send

Business context, the problem you're deciding or auditing, and non-sensitive documents. Access, where an engagement needs it, is scoped read-only by default.

02

What we never ask for

Credentials, production data, payment details, special-category data, or confidential source archives — not in the public enquiry, and not before a signed data schedule is in place.

03

Providers & retention

Work runs through the AI providers and access controls agreed in the engagement's data schedule. Working data is deleted on a stated schedule after closeout, subject to statutory financial-record requirements.

04

NDA & DPA

An NDA or DPA is available before we handle anything sensitive — ask at the fit check, before any deposit or data changes hands.

03 — Process

How an engagement
runs, start to finish.

One path for every offer. Fixed price, cleared funds before delivery starts, cleared balance before final handover.

  1. Step 01

    Fit check

    Tell us the outcome you need. We confirm fit, the likely offer, and a price range — within one working day, with no acceptance promised yet.

  2. Step 02

    Scope & SOW

    Deliverables, exclusions, safe inputs, acceptance criteria, timeline, and price get locked in a signed statement of work.

  3. Step 03

    50% deposit

    A numbered invoice goes out on signature. Work starts once the deposit clears our bank account — a transfer screenshot is never treated as proof of payment.

  4. Step 04

    Delivery

    We work the locked scope and send agreed status updates. You supply only the safe inputs the SOW defines — never credentials or production data.

  5. Step 05

    QA & correction

    You review a factual-check draft (Audit offers) or staging/branch UAT (Sprint) against the signed criteria, with one bounded correction round.

  6. Step 06

    Balance & handover

    A numbered balance invoice goes out. The final report, code, or assets hand over by bank transfer against that invoice, once funds clear — stated plainly, never on this site.

04 — Proof

Our own builds,
labelled honestly.

No invented clients, logos, or metrics. These are Appaya's own internal builds, not client engagements — disclosed as exactly that.

Internal build · not a client engagement

Staige

AI virtual staging for UK estate agents — upload empty-room photos, get furnished renders back. Designed and built end to end the Appaya way, ahead of its own public launch.

Internal build · not a client engagement

ActionPack

A set of focused deposit, invoice, and planning utilities, built and run from one shared codebase as Appaya's own operating tools.

05 — How we work

Every change passes an adversarial cross-engine review before it ever reaches you. That's how we guarantee the quality.

The rigor isn't a promise on this page — it's a gate in the pipeline, and the proof ships with the work. Premium delivery, priced like it.

Fixed price, signed SOW

Every engagement is scoped, priced, and signed before any deposit — no hourly meter, no scope creep.

50% deposit, 50% balance

Work starts on a cleared deposit against a numbered invoice; final handover follows a cleared balance.

One correction round

Every offer includes one bounded factual-correction or defect-remedy round against the signed criteria.

06 — Questions

The honest
answers.

Which offer do I need?

Start with the audit unless you already know exactly what needs building. You have shipped something with AI assistance and want an honest read on it → AI Codebase Audit. You need ongoing senior technical judgement, not a one-off → fractional leadership. You have one bounded, already-defined outcome → Fixed-Scope Build Sprint.

What does an engagement cost?

Each offer is fixed price, quoted after a short fit check — you know the number before any deposit. A 50% deposit reserves the slot; the 50% balance is due before final handover. No hourly meters, no surprise invoices.

Do AI agents do all the work?

Agents do the volume, working in parallel lanes across Claude, Codex, Gemini, and more. A human directs every lane, and nothing ships until it passes an adversarial cross-engine review. Speed comes from the fleet; trust comes from the gate.

Who owns what you build?

You do. On the Sprint offer, full ownership of the code and assets transfers on cleared final payment. On both audits, the report and its findings are yours outright on delivery.

How do you handle sensitive data?

We never ask for credentials, production data, or payment details in the public enquiry. See Data & confidentiality above — an NDA or DPA is available before anything sensitive changes hands.

How do I start?

Use the enquiry form below, or send one email to hai (at) appaya.co with what you're deciding, auditing, or building. A human replies within one working day.

Who's behind Appaya

Appaya is founded and directed by Luke Czak — ex-CPTO, with 12 years leading product and technology in UK regulated fintech, from Series A startups to global banks.

He scopes the work, steers the fleets, and signs off every build before it ships.

More about Luke — lukeczak.com

Hai. Let's talk.

Request a fit check.

Tell us what you're deciding, auditing, or building. A human replies within one working day — qualification, scope, SOW, and the private deposit invoice all happen after this, never on this page.

Or email hai (at) appaya.co directly