Every week you are not live, the market belongs to someone else. The speed comes out of the overhead, not the quality.
Week 01
Scope locked
Architecture, risks and a fixed price. Days, not a research phase.
Week 02
A build you can open
A real URL you can log into. It never goes dark after this.
Week 04
Feature-complete beta
Core loop working, first testers inside it.
Week 06
Live, on your accounts
Production on your domain and repo. Then 90 days on call.
01A foundation, not an empty repo
Auth, roles, billing, audit logging, CI, monitoring — already written. Week one starts at the part that is yours.
02One team, no handoffs
Design and engineering on the same call. A sprint of tickets becomes an afternoon.
03Decisions in hours
One decision-maker each side, a slot every working day. Nothing queues for a week.
04Something ships every Friday
A deployable build from week two. You check progress by opening it.
Capabilities
What we build
Five disciplines, one team, and a single path from the first call to launch day.
01
From idea to launched
The same six weeks from your side of the table: what we ask of you, what you decide, and exactly what you hold at the end of each stage.
Week 0 · free
Validate
We pressure-test the idea before anyone writes code. If it should not be built, we say so.
A one-page briefYour partNinety minutes and an honest answer about who this is for.
Week 1
Scope
Architecture, risks, and the smallest version worth putting in front of a user.
A number that does not driftYour partOne decision-maker named, and the must-haves separated from the wants.
Weeks 2–6
Design & build
Design and engineering as one team. You open a working build every Friday.
Your product, weeklyYour partThirty minutes on a Friday to open the build and say what is wrong.
Week 6
Launch
We ship it, hand over the keys, and sit through the first day with you.
The code, accounts and docsYour partA domain, and someone on your side to hold the keys.
90 days
On call
Ninety days of support included. A retainer after that, only if you still want us.
A number that answersYour partTell us what broke. That is the whole process.
What gets built
AI products · Enterprise & ERP · IoT & connected systems · SaaS platforms · MVPs · Mobile
02
AI, past the demo
Products people keep using after the novelty wears off.
Chat that knows your business
We wire the model into the systems that actually run your company — ledgers, tickets, documents, your own APIs — so every answer cites a record. Anything expensive or irreversible stops for a named human, by design.
Cleared 12 March — $8,240 by ACH, reference 9F2C.
billing_ledger · payments_api
Refund it.
Held for approval
That is over your $5,000 limit, so I have not sent it.
Queued for Sara with the invoice attached.
policy · refund_limit_v3
Ask about an invoice, a customer, a policy…
Assistants & copilots
In-product chat grounded in your documents and databases.
Voice & phone agents
Answer, qualify, book — then hand to a human where you decide.
Automation with a gate
Drafting and routing run unattended. Costly actions wait for a name.
Evals & guardrails
A test suite for a non-deterministic system, plus PII redaction.
Built hereArdenta is our own AI front desk: answers around the clock, cites the document it used, books into the calendar, keeps your existing number.
Join the waitlist →
03
Enterprise & connected
ERP and operations platforms, and the devices that feed them.
Enterprise & ERP
The system the company runs on
HR and payroll, finance, inventory, procurement, field operations. Built as one platform with real roles and a real audit trail — not nine tools and a spreadsheet holding them together.
ERP & HRMS
Payroll & finance
Integrations
SOC 2
IoT & connected
Hardware that reports for duty
Fleets, sensors, access control and device policy, wired to dashboards people act on. Telemetry that arrives, commands that land, and a record of both.
MQTT / BLE
Telemetry
Device policy
Edge & gateway
01
Append-only audit trail
02
Least privilege, ours included
03
Encryption & key custody
04
Data residency you can point at
05
The evidence pack
Regulated work
Healthcare and finance builds carry these from week one — HIPAA, PCI DSS, SOC 2, ISO 27001. We build to the controls and hand you the evidence; the certificate is issued to you by your auditor.
04
Interface & Interactive
The part people call the product. Interfaces with a point of view, motion with a reason.
Launches, rebrands, campaign pages. Fast enough to score green across the board, distinct enough to be remembered after the tab is closed.
Dashboards, consoles, and tools people sit inside for eight hours. We sweat the empty states, the keyboard paths, and the thousand-row tables.
Scroll stories, launches with a pulse, product films embedded where they convert. This is where the film side of Manzar earns its keep.
05
Design Systems
The product behind the product. One language every screen speaks.
Aa
Tokens & theming
Color, type, and spacing as data. Dark mode stops being a rebuild.
⌘
Component libraries
Accessible, documented, versioned. Figma and code that agree with each other.
¶
Docs & governance
Contribution rules and changelogs, so the system outlives its authors.
◎
Accessibility
WCAG AA as a floor, not a feature. Audited with real assistive tech.
Selected work
The proof
Six sites, designed and built end to end. Pick one from either side, then rest your cursor on the screen — or click it — and use the real thing.
Hover or click to use itesc to exit
This one will not run inside a frame.Open it in a tab ↗
Standby
01/06
NORTHLIGHT
Product engineering · Copenhagen & Lisbon
WebGL and GSAP, with a panel that re-themes the whole site live.
You will not be handed to an account manager. The people who scope your project are the ones who write it, and they stay in every call until it is live.
If a deadline is wrong you hear it in week one, not week eleven.
UzairFounder, Manzar
70%Of new work comes from clients we have already shipped for
90Days on call after every launch, included as standard
2Studios, Lahore and Paris, one team across both
Before you commit
What we put in writing
Budgets drift, dates slip quietly, teams go dark after launch. Six clauses answer that — and all six are in the agreement, not just on this page.
01Budget drift
The price is fixed at the end of discovery.
One number, approved by you at the end of the scoping week. It moves only if you change the scope in writing.
02Nothing to show
A working build lands every Friday.
From week two you get a URL, not a status report. Progress you cannot open is not progress.
03Vendor lock-in
Every account is opened in your name.
Repo, cloud, domain, design files — opened under your organisation in week one. Nothing to migrate at the end.
04The late surprise
You hear bad news the week we know it.
A date at risk or an approach that is not working goes in that Monday’s note, not week eleven’s.
05The team that vanishes
Ninety days of support come with the launch.
Included, not invoiced. A written runbook, a recorded walkthrough, and the same people on the same channel.
06Signing blind
Scoping ends in a decision, not an obligation.
The brief, the architecture and the estimate are yours whatever you decide next.
Standard terms
The agreement goes out unredacted after the first call.
Request a copy →
Before you ask
FAQ
“If your question isn't here, it fits in an email. We read everything that lands in the inbox.”
RESPONSE TIMEUnder 24h
Six weeks from signed scope to a product real users can log into. An openable build in week two, a feature-complete beta around week four. Tell us your date on the first call — if it can't be held you'll hear that immediately, not in week eleven.
Yes. Assistants and copilots inside your product, voice and phone agents, and automation with a human gate on anything irreversible — all grounded in your own data so answers cite a record. Evals, PII redaction and fallbacks come with the build.
Yes. Those controls go in from week one — append-only audit trails, least privilege, managed keys, data residency — and the evidence pack ships with the code. The certificate is issued to you by your auditor; we make sure nothing in the build stands between you and it.
With a call and a one-page brief we write for you, free. If we're not the right fit, we'll say so and point you to someone who is.
Scoping sprints start around $6k. Full builds typically run $25k to $120k depending on scope. You get the number after scoping, and it doesn't drift.
The same senior team that scoped it, plus specialists we bring in by name when a project needs them. You meet everyone who touches the codebase. Nothing is outsourced anonymously.
An MVP in about six weeks. A marketing site in three to five. A larger v1 platform in eight to fourteen. You open a working build every Friday from week two either way.
Ninety days of included support, then a retainer if you want us on call. Either way you own the code, the accounts, and the docs.
