Digital studio · Lahore · working worldwide

Everything a business needs built — and kept running.

Why the name

Let us do some lightening
in your tech problems.

Lightening, not lightning. The work is making a heavy thing lighter — fewer moving parts, fewer people to chase, fewer things you have to hold in your head to keep it all running.

  • One brief

    Not five. Hiring separately is five briefs written by you, five versions of your business explained from scratch, and five suppliers who each blame the other one.

  • One catalogue

    Two hundred services in eighteen categories. Which one your problem turns out to be is decided after the questions, not before them.

  • One number

    A starting rate and a delivery time printed on every service page, before you contact anyone. You should be able to tell whether something is within reach without spending a week finding out.

The first conversation

Nobody arrives asking for a service.

You describe what is going wrong. Turning that sentence into the right piece of work is the job — you should not have to know the name of the service that does it.

  • "The site is slow."

    Speed & Core Web Vitals optimisation

    Slow for you on desktop broadband is a different problem from slow for a visitor on mobile data, and only the second one costs you anything. The question that settles it is which page felt slow and on what device, because if the server itself takes two seconds to answer, the honest fix is managed hosting and no amount of front-end work will reach it.

  • "I need an app."

    Progressive Web App (PWA)

    Often this means something a customer opens on a phone and comes back to, which a Progressive Web App does inside the browser. The question that settles it is whether it has to install from an app store and reach the camera, offline storage or push notifications. If it does not, a browser is enough, and we will say so before you spend on a native app you do not need.

  • "People should be able to book themselves."

    Booking & appointment system

    The form is the easy half. The question that settles it is the rules behind it — session length, the gap between appointments, how far ahead people can book, holidays, and what happens when someone cancels — because that answer, not the design, sets the size of the job.

  • "People reach the checkout and leave."

    Product page CRO

    A frequent cause is the shipping cost appearing at the final step, or an Add to Cart button that sits below the fold on a phone. The question that settles it is which exact step they drop at and when they first see the total, and if the answer points to a settings change rather than a redesign, we will tell you that instead of selling you the redesign.

  • "We don't come up on Google."

    Technical SEO audit

    Not being indexed and not ranking are two different failures with two different fixes, and the same sentence describes both. The question that settles it is how many of your pages are actually in the index. If the answer is most of them, the work is content and competition, and a technical audit is the wrong purchase.

  • "Train the AI on our data."

    RAG knowledge assistant

    This almost never means fine-tuning, which is slower and dearer than what is being asked for. The question that settles it is whether you want answers drawn from your documents or writing that sounds like you — the first is a retrieval system, the second is a prompt, and only a narrow third case justifies training a model.

  • "It should all just be automatic."

    Ops audit → automation roadmap

    Put that way, it means the bottleneck has not been found yet, and building automations before finding it spends money on the wrong step. The question that settles it is simple and unwelcome: show us the task happening once, live, on your screen. The version in your head and the version your team runs are rarely the same.

If your sentence is not on this list, it still translates. Describe what is going wrong and the service name is our problem.

The range

Two hundred services, so the answer is not decided in advance

Eighteen categories, six practices. The count is not the point. The point is that the diagnosis and the work can come from the same place.

  • Why 18 categories

    Whoever you ask decides what you buy

    Ask a shop that builds apps whether you need an app, and the answer was written before you arrived. It is not dishonesty. A person who sells one thing hears that one thing in every problem, and you have no way to check. Eighteen categories exist so the diagnosis is not settled before the conversation starts. What you describe as a website problem is often a checkout problem, or a data problem, or an operations problem wearing a website's clothes. Which category the work ends up in is decided after the questions, not before them.

    18 categories · 6 practices

  • The spread of price

    $15 and $200,000 come off the same list

    The lowest whole-job price on this list is $50, and the lowest rate of any kind is $15 for a single edited video. The highest ceiling is $200,000. That spread is deliberate, and its first consequence is a pricing one: nobody has to be pushed up a tier to make a project worth doing. Small work is how you find out whether we are worth the large work, so it is quoted as its own job rather than as a way into a bigger one. If the honest answer is the small job, the small job is what gets quoted.

    $15 to $200,000

  • The spread of time

    Most of it runs in weeks. Forty-one never finish.

    Twelve services are delivered in days. One hundred and seventeen run in weeks, 27 in months, and 41 do not end at all. Two more are sold per engagement and one is an emergency line, which is the whole catalogue accounted for. That last group is the one people skip. A site that ships is not a site that keeps working, and those 41 exist because that work has no finish line to reach, which is why most of them are billed by the month rather than by the piece. The work measured in days and the work measured in months are the two ends of one list, and working out which end your problem sits at is most of the first conversation.

    12 days · 117 weeks · 27 months · 41 ongoing · 3 other

  • Who this is for

    155 different descriptions of who buys

    Across the catalogue there are 155 distinct descriptions of who buys. Some are as wide as "Any site owner". Others are narrow enough to be one bad week: "Breached companies". "Hacked site owners". "Sites that were hit". If that is you this morning, you are not shopping in the same catalogue as somebody choosing a brand identity, and you should not have to read past their work to find yours. "Frustrated owners" is the row for finishing what another developer left half-built, and if that is you, you already knew which one it was. "Amazon sellers" and "Struggling advertisers" are two more. Writing each buyer down separately is what stops a list of services turning into a list of nouns.

    155 buyer types

  • Six practices

    Ten of the 200 sell no build at all

    The 18 categories group into six practices: Build & Design 55, Growth & Marketing 42, AI, Automation & Data 35, Platform, Security & Operations 35, Immersive, Web3 & Media 23, and Consulting, Product & Talent 10. The shape tells you where the weight sits. The smallest group is the one worth reading twice. Those ten produce a document rather than a deployment: a specification, a roadmap, a review of a system before you buy it. They carry a price like everything else, and where the work genuinely has no end date the catalogue says so instead of inventing one, because sometimes the finished piece of work is a decision, and a decision has to be purchasable on its own or it never gets made.

    Build 55 · Growth 42 · AI & Data 35 · Platform 35 · Media 23 · Consulting 10

  • In practice

    One brief instead of five

    Hiring separately is not just five invoices. It is five briefs written by you, five versions of your business explained from scratch, and five suppliers who each point at the other when the contact form stops sending. These sit in one place for a plainer reason than breadth: when the tracking breaks, the tracking is a service on the same list, quoted the same way as the site it sits on. Buying one thing is a complete transaction and it ends there. The second one does not start the explaining over.

    One brief, one catalogue

The catalogue is wide so that the diagnosis can be narrow.

What things cost

Every price on this site is printed before you ask.

Each service carries a starting rate and a delivery time you can read without filling in a form. What follows is what those numbers mean, and what moves them.

  • Published, all 200

    The numbers are already on the page

    Every one of the 200 services here shows a starting rate and a delivery time on its own page, before you contact anyone. There are no exceptions to that; no row is missing either field. 122 of them start under $1,000 and 66 go above $10,000, which should tell you these are not one kind of work priced one way. Delivery is printed the same way it is quoted: in days, in weeks, in months, or as work that does not end. The reason for printing any of it is plain. You should be able to tell whether something is within reach without spending a week of emails finding out.

    200 services

  • Reading a range

    What a range actually means

    A range is two different jobs, not an opening price and a negotiation. 147 of the 200 are printed as a plain minimum and maximum. The other 53 carry a unit, a plus or a percentage instead, because that is how that particular work is actually bought, and the unit is named on the page rather than explained later. Four things decide where inside a range you land. How much you are actually asking for, which is nearly always larger than the first sentence of the brief. How old the platform is, because a current stack comes with tooling and an older custom build comes with none, so the same change has to be made by hand and tested by hand. How much already exists, since copy that is written, photographs that are taken and records that are clean shorten the work. And how many third parties have to agree, because a payment provider, a CRM and an ad platform each bring their own limits, their own approval queue and their own way of breaking.

    155 of 200 are a plain range

  • Retainer or project

    A retainer buys something a project cannot

    39 of the 200 are priced monthly. Three are billed by the hour. The difference between a retainer and a project matters more than the amount. A project ends: something is built, handed over, and the invoice closes. A retainer is for work that is the same work every month — testing, monitoring, patching, search, support, and the report that tells you what happened. Buy a project for a thing that finishes and you get a clean handover. Buy a retainer for that same thing and you pay for months in which nothing needed doing. The mistake runs the other way too, and that one is the expensive one: a security patch, a broken checkout or a ranking that is sliding is not a one-off purchase, and treating it as one means buying the same emergency again at emergency rates. Hourly is deliberately rare here, because it prices the clock instead of the result, and the clock is the wrong thing for you to be buying.

    39 monthly · 3 hourly

  • Stated, not buried

    What the number does not cover

    The list of what is excluded is more useful than the list of what is included, so it gets written down first. Writing and translating copy. Selecting, licensing and editing photographs. Migrating old posts and old records out of wherever they currently live. Training beyond the handover session. Revisions past the rounds agreed in writing. Changes that arrive after you have signed off on staging. Monthly fees for third-party tools, and hosting. None of these are hidden charges and none of them are refused. They are quoted separately because folding them into one figure is how a price stops meaning anything, and how a fixed quote quietly turns into an argument later on.

  • Before the quote, the look

    What has to happen before a number means anything

    Printing a range is honest. Turning that range into a quote without opening your site, your data or your existing build is not. That number is wrong in one of two directions. Too low, and it gets renegotiated when you are halfway in and have no easy way out. Too high, and you have paid a premium for someone else's uncertainty. So the look comes first, bounded and priced on its own — where a live site is involved that look is the audit, and it comes back with evidence rather than an opinion. Then the number, in writing, set against named deliverables. Ask for a figure over a message and you will get the published range, plus a straight answer that a range is not yet a quote.

The range is public. The quote comes after the look, and it says exactly what it covers.

Into the work.

Eighteen categories, 200 services — the whole catalogue, one station at a time.

Two of the stops are not services at all. They are the two things this studio refuses to do.

Every build, underneath

Eighteen categories. One shape underneath all of them.

  1. 01

    Data

    What the system is allowed to know, and where it came from.

  2. 02

    Model

    The rule, trained or written, that turns that into an answer.

  3. 03

    Evaluation

    A set held back on purpose, so the answer can be wrong in private first.

  4. 04

    Deployment

    Shipped with the way back already built, not discovered later.

  5. 05

    Monitoring

    The part with no end date, because the world it reads keeps moving.

A booking form and a vision model are not the same job. They fail in the same five places.

How the work runs

Project work runs through the same five steps.

A booking system and a brand identity are not the same job. The sequence they run through is the same one, and it is fixed before anyone opens an editor. Retainers and hourly work do not run this way — there is no handover on work that never ends.

  • 01

    A call before a number

    The first message is never enough to price. "I need a website" and "we need AI" are solutions, not problems, and a figure quoted against either one is a guess. So what you get first is a call with a set length, and it ends where it was set to end. We ask what the work has to produce: a phone call, a filled form, a sale, a record that somebody changes later. We ask who signs it off, because approval sitting with a person who is not on the call changes the shape of the whole project. We ask what happens if nothing is done at all, because a problem that is costing nothing is not a project yet. And we ask what you have budgeted, out loud, because it is the fastest way to find out whether there is a job here at all. If you would rather not name a number, we name a small version, a middle one and the whole thing, with what sits inside each. You will not get advice on this call. Advice about a system nobody has opened yet is a guess.

    Before a number

  • 02

    Scope you can count

    The proposal is short, and there is no section about our values. It names what you get: the pages by name and by count, the workflows, the fields, the screens, the files. Adjectives come out, because "modern", "clean" and "professional" cannot be checked against anything at the end, and unverifiable words are what a project argues about in its final week. Beside that list sits the longer one, which is what is not included. Anything you assumed was in and we assumed was out belongs on that page before you pay, not in a message afterwards. And it opens with your own problem in your own words, so you can tell immediately whether we listened or just nodded.

    Before you pay

  • 03

    The price and the date are fixed first

    You get a number, not a meter that runs: one figure, agreed in writing, before anyone starts. Where a service is priced by the month, by the hour or by the unit, the proposal says which of those it is and what one unit buys, so the figure you approve is the figure the invoice uses. Payment is split, and the first part clears before a file is opened. The date works the same way. It is a real date, and it starts counting from the day we have what we need from you, not from the day you say yes. Work runs late because copy has not arrived and an admin login has not been granted far more often than because the work itself was hard. So the proposal names what you owe us and when: the logins, the text, the images, the person whose hour we need. It also says what happens if those do not arrive, which is that we build on placeholders, go live, and the real material becomes its own small job with its own price.

    Before anything starts

  • 04

    You get a link, not a status report

    What you get first is not a percentage complete and not a summary of what was done. It is a link: a page, a screen, or a workflow that runs once and leaves behind a row you can look at. Building in silence and revealing the whole thing at the end is how a misunderstanding gets expensive, because it is made in the first days and paid for in the last. So the first thing you can open is deliberately the smallest version that runs the whole way through, and the longer the job runs, the more often you see it moving. Review happens on a staging link, opened on your own phone as well as on a laptop, and we ask for your changes as one list rather than in messages spread over several days. Every item on that list comes back marked: doing it, not doing it, or costs extra, and you see those marks before we act on any of them. Then the same written checklist runs before anything goes live. Every link clicked. Every form submitted to a real inbox and confirmed to have landed there. Redirects in place, the previous version backed up. A checklist held in your head is not a checklist.

    Days to months

  • 05

    Handover with the keys in it

    Before anything is handed over, we break it on purpose. The API key gets changed to see whether the alert actually fires. A malformed message goes in to find out whether the thing fails loudly or fails silently, because silent failure is the one you discover months later, once the orders have already gone missing. Then you get all of it: the code, the accounts, the passwords, the admin access with your name in the owner seat rather than ours, a recording of the thing being used by a person, and one page saying what each part does and what to do when it stops. Nothing is kept back as leverage. If we vanished tomorrow, somebody else could pick this up from what is already in your hands. What support follows handover is written into your own proposal rather than promised here, because the shortest job on this list and the longest cannot honestly carry the same window. Where a monthly arrangement genuinely applies it is offered after the work is finished, as a separate decision, never as the condition for receiving your own files.

    Handover

The price and the calendar change with the job. The order of the work does not.

Every engagement starts with a measurement — and with what the measurement could not reach.

The audit is the studio’s smallest product and its whole method: fifteen categories run on the page a visitor actually sees, and a plain list of every check that could not complete. The same rule governs the other 200 services — what was measured is reported with its source, and what was not is said out loud.

Get my audit

Lighthouse · axe-core · headless Chromium · nuclei · retire.js · W3C validator

  1. 01Performancechecked
  2. 02SEOchecked
  3. 03Securitychecked
  4. 04Accessibilitychecked
  5. 05Functionalnot reachable — said so
  6. 06Responsivechecked
  7. 07Contentskipped: no page there
  8. 08UXchecked
  9. 09Analyticschecked
  10. 10Privacy / Legalnot reachable — said so
  11. 11Hosting / Infrachecked
  12. 12Code Qualitychecked
  13. 13Socialchecked
  14. 14Trust & Conversionskipped: no page there
  15. 15Local SEOnot reachable — said so
See a Real report

Robotic AI, software side

Machines act in a world that moves. We rewrite the software when it does.

We build what a system sees, what it decides, the twin it is tested against, the devices it commands. Cameras move, floors change, models drift. So that layer keeps being rewritten. It is not a phase we close.

Robotic AI

We keep building the software a machine acts on. We do not build machines.

What we refuse

What we will not do, and the reason in each case.

Each of these is on the list because it can be checked, not because it sounds principled.

  • Checkable, or not

    A ranking, a score, or any number we do not control

    Two kinds of promise are easy to mix together. One kind can be proved on a screen after the work is done: the broken links are gone, the schema validates, the page paints faster for real visitors on real phones. The other kind belongs to Google, or to an ad auction, or to your own customers. We can work on it. We cannot promise it. So the contract carries only the first kind, and the second is written down as the goal the work is aimed at, where it can be measured without being owed. A ranking is not ours to give. Neither is a performance score, which is a lab simulation on one device nobody in your audience owns.

  • The smaller answer

    Work you do not need yet

    This is the one that costs us money, so here is the mechanism rather than the sentiment. When you ask whether you need the thing we sell, our answer has our own interest attached to it. The only honest way to hand that answer over is with the evidence beside it, so you can check the reasoning instead of trusting the person holding it. A record that only one organisation writes to needs a database, not a chain. A sales team quoting from a stock sheet that updates after the day's orders have already gone out has a timing problem, and no new system fixes a reporting delay by existing. In both cases the work that follows is smaller than the work that was asked for, and it is on the same list, priced and dated the same way.

  • After launch

    A promise that it will keep running on its own

    Anything built against someone else's system has a clock on it. APIs change. Platforms change their rules. Tokens expire. A payment provider renames a field and a working integration stops working on a Tuesday morning. So we will not tell you a build is finished forever, and we will not tell you it will never make a mistake. It is also why part of this catalogue is not a project at all — not a subscription bolted onto a build, but the part of the work that has no end to hand over. What we will tell you is what happens when it breaks: the system reports its own failure instead of swallowing it, and the window in which it gets fixed is named in writing before you sign, not decided on the morning it goes wrong.

Everything above this is what we will do, priced and dated. This is the part that is not for sale.

Tell us the problem, not the service.

Start a project.

200 services Audit from £499

Next — Free tools