Your studio · Remote · Pay as you go · You design, I build
You already sold the look. You keep the client, the Figma and the brand. Point your staging hostname at my server; the site comes up on your URL, as if your studio built it. When you pay in full, you receive the code to deploy, or I deploy it for you. Remote only. Pay as you go. No desk in your studio, no retainer, and no letter to your client’s inbox.
Figma is the design file you already sold: pages, type, colour and components. You send that. I do not open a blank canvas. Your file becomes working pages you can present.
Figma · the brief you send, and I build
Pulse · The trade press
Headlines from the journals professionals already read: TechCrunch, HubSpot, Ahrefs, Search Engine Journal and the rest. I do not write this. It is a live feed of the web and e-commerce trade, gathered here so you can skim it between jobs. Read only.
01 · Why the overflow you buy so often fails
Hiring a developer for feast-and-famine work is the wrong expense for your studio. Offshore is the wrong risk. A retainer is payment for an empty chair. I fill the gap: you buy a scoped job, done remotely, then the clock stops.
Your pipeline is feast and famine. A hire means salary, National Insurance, a chair, and paying them to sit idle between jobs. You do not need someone in the office. You need hours when a build is live. I work remotely. When your job is delivered, the clock stops.
You have paid for reserved days that sit unused in a quiet month. Pay as you go means you buy the slice in front of you: this template, this checkout, this plugin. No rolling contract, no unused days, no period of notice.
The demo looks done until you open it: spacing that ignores your Figma, pages that fail accessibility checks, cookie banners that do not meet UK rules, checkout that gets VAT wrong, WordPress that breaks on the next update. Their time zone costs you a day on every review. I work UK hours, to UK data rules, on a staging address you can put in front of your client.
A footer credit, a “quick question” to your client’s inbox, a pitch six months later. Your relationship is the product. I stay off that correspondence. An NDA first. Your brand on the work. I do the work; there is no bench behind the name.
Code in the vendor’s repository, credentials in their hosting, no assignment. Switching later means a rebuild you have to fund. With me you point your staging hostname at my server, so the preview still looks like your build. When you pay in full, you receive the repository to deploy, or I deploy it for you. Intellectual property goes with the files.
The shop you hired rewrites the art direction you sold, argues over UX, or insists your client join every call. You already sold the design. I take your Figma and implement it. No redesign. No client call unless you ask.
02 · How your job runs
You point a hostname you already own, such as staging.youragency.com, at my server. The build appears on your URL, under your brand, as if your studio is shipping it. I write the PHP, WordPress, Woo, Laravel or Vue there. When the remaining 50% is paid, you receive the code to deploy yourself, or I deploy it for you.
03 · What I code for you
WordPress, WooCommerce, Laravel, Vue, APIs, checkouts, and the rescue when a build of yours is stuck. You supply the look and the copy. I build the system under your brand.
Custom themes and the admin your client will actually open. Versioned, maintainable, not a heap of abandoned add-ons. Survives the next WordPress update.
Stores wired to Stripe, PayPal or Worldpay. Checkouts that convert, webhooks that do not drop, refunds that reconcile. UK VAT that matches the till.
When a CMS is the wrong box for the job you sold: configurators, directories, member areas and the workflows your client’s operators actually live in. I am on your brief. No bench.
Auth, queues, domain logic, JSON the front end can trust. The unglamorous work that keeps a product of yours online at two in the morning, without a junior sent in your place.
Routes, inspections, bookings, order boards. Vue and TypeScript on data you already have. You present it; I remain off your client’s call.
A site of yours that has gone down, a slow homepage, a checkout that will not take the card, a plugin fight after an update. A scoped fix, then the clock stops. Same terms as a new build.
Branding, art direction, UX workshops, copywriting, mood boards. If the job is “make it look nicer,” that stays with you. If the job is “make the Figma work,” that is me.
04 · The kit
PHP, WordPress, Woo, Laravel, Vue, Stripe, PayPal, Worldpay. UK hours, UK GDPR, Warwick-based. You do not need offshore transfer paperwork.
Separated by commas. Matches the tools you can name on a job.
PHP, Node and the JavaScript UI kits you can name when you send the brief.
Content systems and storefronts you already sell: WordPress to headless, Magento to Shopify.
CSS systems, component kits and client-side state: the layer your client actually sees.
Build, deploy and day-to-day kit you can put on a job: Composer and npm through to Apache.
Relational truth, document stores, cache, search and the ORMs I wire for you.
Hosts, CDNs and platforms you can put on the brief: from a cPanel box to an edge network.
Unit, browser, a11y and performance checks so the release you show your client is not a guess.
Handoffs, assistants and model APIs I can wire into the same stack as the rest of your site.
UK and international rails you can name at checkout: cards, wallets, invoices and pay-later, wired in, not bolted on.
Lists, ads, analytics and the tags that tell you whether the site you sold is actually earning.
Current kit
Vite, Laravel, Vue, Tailwind, Stripe, Playwright, Cloudflare. You send the file; I wire it under your brand.
For experiments
We're just tidying up some of the code...
Upload a night-sky photograph to find and count stars, then explore each detection in the image.
Open experiment05 · Proof
Private due to NDA
Names stay off the page. The work does not. This is the kind of code I have shipped under other studios’ brands, and would ship under yours: routes, checkouts, configurators, dashboards, the unglamorous admin a real team will open. Your client never sees my name. That is the product you are buying.
Goods-planning software that builds a day’s runs from fleet, load, service type and place, then lets a planner split a route and print the driver pack. Maps, allocation, the board a warehouse actually opens.
A multi-purpose cloud: templates, remote updates, site sync. Built so the product could sit behind more than one face without leaking the people on it.
High-brightness digital signage for hospitality. A template library, remote push, venues staying in sync. The screen the floor staff actually point at.
The core of a finder: nearby, available, the job landing with the right person. Capture, route, handover. Not a brochure with a form on it.
Range, cart, UK checkout, stock that matched the till. Stripe, PayPal, Worldpay as the brief asked. A small brand that could actually run the shop.
Catalogue, payments, the rebuild a retailer points a customer at. Not a theme with the logo swapped. The live store, from a Figma already sold to the client.
Forms in the field, reports that print, the board a safety inspector actually uses. Playground-grade process, not a generic CRM skin.
WCAG as the brief, not a plugin ticked at the end. An admin a trustee can open. The public site a disabled visitor can actually use.
A trade buyer assembles a product from parts and sees the figure before it hits the cart. Woo, analytics, the kind of tool that replaces a PDF and a phone call.
Thousands of SKUs, filters that do not die, Magento under a retailer’s load. That depth of catalogue, without putting a name on this page.
When the brief was campaigns, not carts. Forms, lists, the tracking you already promised your client. Wired in, not a second website.
Updates, gateways, the unglamorous care that keeps a live shop alive. Local retailers, ongoing, the work nobody puts in a case study unless it fails.
White-label is the arrangement you are buying: you point your staging at my server, I build, you present. It looks as if your studio shipped it. After full payment you receive the code to deploy, or I deploy it for you. Your client never sees my name.
Ryan Ormrod · white-label, your brand
06 · The offer
A 50% deposit starts your job. If you withdraw, unused hours from that deposit are returned. Hours already worked are retained. Code and intellectual property move to you only when the remaining 50% is paid. Choose a stage on the chart.
Pay as you go
You do not hire me. You do not retain me. You buy a defined job, point your staging at my server, and stop paying when it is paid in full. Your first job and your tenth job are the same terms.
No desk in your studio. No “can you come in on Tuesday.” I am not on your Slack all day between projects. UK hours whilst your job is live, then off the clock.
You buy a defined job: this template, this checkout, this plugin. Not a person for the month. The figure follows your Figma, not a public grid.
No retainer, no minimum hours, no rolling notice. Withdraw after one build. An NDA still exists so your client stays protected. That is the only paperwork that matters before files move to you.
You point your staging at my server whilst the deposit is live. Unused hours from that deposit come back if you stop. When the remaining 50% clears, you receive the code to deploy, or I deploy it for you. You present it as your work. Payment then stops.
Time at £30/hr. UK invoice, no VAT. The quotation follows your brief, not a catalogue. Send the Figma, receive a figure for that slice.
07 · Send a job
Send your studio name, the slice, the stack, the Figma, and the staging hostname you will point at my server. Include a digital NDA link with the brief, not a file. I quote that job and stay off your client’s inbox.