Cultiver
Hospitality & Homeware · Bed Linen · Sydney, Australia
A bespoke Shopify storefront for a premium linen brand.
Read the case study : CultiverDesign that ships,
exactly as designed.
UI/UX, web design and brand identity from one senior team: researched before it's drawn, delivered as a system, and buildable by the same people who designed it, so what you approved is what your users get.
Reply within four business hours (typical)
Brands our teams have delivered for
What we do
PixelCrayons designs product UI, marketing websites and brand identities, and can build what it designs. Every engagement starts with research, ships as a reusable design system, and ends in dev-ready files, or production front-end code from the same team. WCAG 2.1 AA accessibility is a default, not an upsell. Direct for brands, white-label for agencies.
- Research before pixelsInterviews, analytics and journey mapping before anything is drawn, so reviews debate evidence.
- Systems, not one-off screensEvery colour, component and layout rule named and documented, so screen forty matches screen one.
- Dev-ready handoffFiles a developer who has never met us could build from, or production code from our front-end team.
Selected work
Judge the work,
not the adjectives.
Outcomes tied to real engagements, not averages.
2004
Established
500+
Agencies served
4,500+
Projects delivered
340%
Revenue growth · 7 months
eCommerce
+127%
Organic traffic · 5 months
SaaS
85%
Faster delivery · backlog cleared
via agency partner
Where the work happens
Where to start
Start with the problem
you have.
A marketing site that has to convert and rank. A product people can use without a manual. A brand that survives a pitch deck. A Figma file that needs to become a real front-end. Each has its own senior lead; all of it is one team.
01Web DesignNeed a site that converts and ranks? Marketing sites and landing pages tested against your real content, designed to performance budgets we measure after launch.02UI/UX DesignA product people can use without a manual? Research, user flows, clickable prototypes and finished interfaces, tested with users before code.03eCommerce Web DesignA store that looks good but doesn't sell? Product, category and checkout pages for Shopify, WooCommerce and Magento, built to convert.04Brand IdentityA brand that survives a pitch deck? Logo, palette, type and voice delivered as a system your team can apply without us in the room.05Design to CodeA Figma file that needs to become a real front-end? Built pixel-accurate by the team that designed it, so what you approved is what ships.06White-Label DesignAn agency that needs a design bench? Our designers under your brand: NDA-backed, your templates, your client calls.
What we design, we can build.
Most studios hand over a Figma file and wish you luck. The gap between design intent and shipped code goes to whichever developer picks up the ticket next. Our designers and front-end developers sit in the same delivery team, so the interface you approve is the interface that ships: same spacing, same motion, same accessibility. No translation loss, no second agency, no discovering at launch that the build doesn't match the file.
In writing, every time
What a design engagement
actually includes.
01
Research before pixels
Stakeholder interviews, analytics and heatmap review, and user-journey mapping before anything is drawn. Design decisions get written rationale tied to what your users actually do, so reviews debate evidence, not taste. A wrong assumption costs an hour to fix in Figma and weeks to fix in production.
Week 1
02
Systems, not one-off screens
Every colour, size and spacing gets a name (a token), every button and card becomes a component, and the rules for laying them out are written down. Screen forty is then as considered as screen one, and the next campaign page takes hours, not a fresh project. One-off artboards age badly. Systems compound.
Every project
03
Dev-ready handoff
Named layers, documented tokens, redlines (the exact measurements a developer builds from), variants (each state a component can be in) and motion notes a developer who has never met us could build from. Or skip the handoff risk entirely and have our own front-end team ship it as production code.
Every delivery
04
Accessibility as a default
WCAG 2.1 AA contrast, visible focus states, reduced-motion alternatives and semantic structure are in the base spec of every engagement, not an add-on line in the proposal. Accessible design is simply the professional standard.
Included
05
Revisions on a schedule
Review rounds are written into scope before work starts, with consolidated-feedback windows at direction, first-deliverable and pre-handoff stages. Revisions are a planned part of the process, never an open-ended negotiation.
Per round
Selected design work
Real sites,
as they shipped.
Osloob
Exhibitions & Events · Commercial Interiors · Saudi Arabia
One website, in Arabic and English, for every stand, event and space.
Read the case study : Osloob
Resolute Dynamics
Automotive Safety · Connected Vehicles · Dubai, UAE
A B2B website as precise as the technology it sells.
Read the case study : Resolute DynamicsIt has been a pleasure working with your team over the past six months. The quality of work delivered has been consistently excellent, and your reliability has been a key factor in the success of our projects.
The process
Brief to first deliverable,
no mystery in between.
01
Start
Brief and a call
We sign an NDA and talk through your product, your users, your brand and what success looks like.
02
Once the brief is complete
Itemised proposal
We confirm the date your proposal arrives. It lists the research, screens or templates, components, prototypes and review rounds, and the price.
03
Your decision
You sign off
You confirm the scope, the payment and the access we need. Nothing starts before this.
04
Typically 2 to 3 business days later
Research, then a direction
Stakeholder interviews and an audit of your current experience, then visual directions presented with their rationale and one chosen with you.
05
On the date in your proposal
First deliverable
A clickable prototype of priority screens and the foundations of your design system, for structured review. Then the rhythm repeats: design, review, ship.
Inside Prism
Your engagement, week to week,
in one workspace.
Prism is the client workspace where your requests, approvals, tasks and weekly reviews live.
Where the engagement includes it, your design work runs in a Prism workspace you log into: review requests, sign-offs, the task list and the weekly review, with each decision recorded.
- 01
Requests and approvals, in one place
Raise a request in your workspace, approve a piece of work, and see who owns it and when it is due.
- 02
Owned tasks and routines
Every task has one owner and a date. Recurring work runs as a routine, so nothing depends on someone remembering.
- 03
A weekly review with decisions recorded
Each decision is written down with the expectation attached: what we expect to change, and by when.
- 04
Every action recorded, checked against the outcome
What we did and what happened sit side by side, so the next review starts from evidence rather than memory.
How we report it, in Prism
The states ledger,
before a screen is signed off.
What you receive in month one
Design is reported as a set of documents you can review without a walkthrough. In the first month you receive the research summary with the tasks users need to complete, the information architecture with every page and its purpose, and the states ledger listing each screen with its empty, loading, error and success states. Review rounds are logged with the decisions taken and the reasons for them.
- 01Research summary: user tasks, existing friction, and what was observed
- 02Information architecture: every page, its purpose, and how users reach it
- 03States ledger: each screen with empty, loading, error and success states
- 04Component inventory: what is reused, what is new, and where each appears
- 05Decision log: each review round, what changed and why
Related workAl Majed for Oud: a fragrance house's whole catalogue, online in two languages.Fragrance & Oud · eCommerce · A published case in this discipline.
Keep exploring
Industries
Sector constraints,
named upfront.
The disciplines don't change by sector. What changes is which constraint bites first. Four industries we run deep, and the rest of the directory.
Who is accountable
The people accountable
for the work.
Parvessh Agarwal
Founder & CEO
An entrepreneur at heart who connects business analysis, strategy, clear objectives and ROI with practical technology solutions.
LinkedIn →
Saundaraya Gupta
Technical Manager
Brings technical delivery, client communication and project management together so work moves from brief to release smoothly.
LinkedIn →Every engagement
A named coordinator and escalation contact
Know who coordinates your engagement, who owns the work and how to escalate an issue.
All engagements. Roles may be combined and vary with your engagement.
Before you sign
Our commitments
Each one says where it applies and links to its full terms.
Response and start times
We typically respond within four business hours. Eligible engagements can typically start within two to three business days after scope, payment and required access are confirmed.
Business hours are Monday to Friday, 9:00 am to 6:00 pm IST, excluding published company holidays. Typical expectations, not guaranteed service levels.
Full termsClear IP & Ownership Terms
Your materials remain yours. Bespoke deliverable rights, licences and handover are agreed before work starts.
All engagements.
Full termsClear Delivery & Escalation Ownership
Know who coordinates your engagement, who owns the work and how to escalate an issue.
All engagements. Roles may be combined and vary with your engagement.
Full termsHow do we know the work will be good?
Every delivery is reviewed before release by QA, your Project or Account Manager and a senior delivery lead, and you then review it against the acceptance criteria agreed at the start. Our specialists use AI to support delivery, with people responsible for reviewing the work. Applicable development work includes 30 days of corrective maintenance after production launch.
Who owns the ad accounts, the data and the work?
Your materials, data and accounts remain yours, and we prefer to work in advertising and analytics accounts you own, with access delegated to our team. Agreed ownership rights in bespoke deliverables transfer under the engagement terms and applicable payment; third-party software and assets keep their licences. We do not withhold customer-owned data or accounts over a payment dispute.
What if we want to stop?
Cancellation, notice and any renewal terms are written into your proposal or statement of work before you accept it. If an engagement ends early, we hand over completed, paid-for work and list any unfinished work separately. For an eligible specialist trial, you can stop within the trial window and pay nothing for eligible trial hours.
How will we know what you are doing?
Before work starts we agree how often you get updates, what the reports cover and who sends them. You know who coordinates your engagement, who owns the work and how to escalate an issue. For hourly and retainer work, time is recorded in Workstatus, so you can see the time records behind your invoice.
How we handle claims, credentials and your data: group credentials, dated ratings, how case figures are signed off, client permissions and data handling.
How reviews run
Three review windows,
and what each one settles.
Review rounds are written into scope before work starts, with a consolidated-feedback window at direction, first deliverable and pre-handoff. This is what you decide at each one, and what happens if the brief moves.
- 01Research before the first reviewStakeholder interviews and a review of your analytics and heatmaps come first, and every design decision carries written rationale. Reviews then debate evidence about what your users do, not taste.
- 02Window one: directionVisual directions are presented with their rationale. One is chosen with you in the room, so everything after it moves fast instead of hedging.
- 03Window two: first deliverableA clickable prototype of the priority screens and the foundations of the design system. You send consolidated feedback, and it is turned around on a stated schedule.
- 04Window three: before handoffYou review what your developers, or ours, will build from: named layers, documented tokens, redlines, variants and motion notes, inside the WCAG 2.1 AA base spec.
- 05If the brief changesWe say so plainly and re-scope that piece, rather than absorbing it silently and letting the timeline or the quality slip.
The number of review rounds is itemised in every design proposal.
Questions
Frequently
asked.
Indicative ranges are on the rate card, and every proposal is scoped against your brief: a five-page marketing site and a product design system are different jobs. The proposal itemises the research, screens or templates, component library, prototypes, handoff and review rounds. Agencies get white-label rates they can quote onward.
A marketing site is scoped by page and template count; a product UI, brand identity or design system runs longer and is phased so development can start early. The first deliverable is usually research plus a clickable prototype of priority screens. Milestones are written into the scope, and if a date moves, you hear it from us first.
Yes, through our design-to-code service: the same team can ship your interface as production front-end code, with the spacing and motion as specified. Or take the design to your own developers: the files carry tokens, variants and redlines anyone could build from, and we answer their questions during the build at no extra charge.
Review rounds are written into the scope before work starts, at the direction, first-deliverable and pre-handoff stages, so revisions are planned rather than negotiated. Consolidated feedback is turned around on a stated schedule. If the brief itself changes, we say so and re-scope that piece rather than absorbing it silently.
Yes. Partner agencies white-label our design work: your templates and client calls, our designers, with deliverables prepared to present as your studio's. It's NDA-backed. We don't approach the clients you introduce to us for direct business, through the work and for twelve months after the last assignment for that client ends, and it's written into the agreement.
Figma for UI, web and brand-system work, with prototypes shared as live links your team can comment on. Your materials remain yours: rights in the files, components, tokens and documentation, their licences and the handover are agreed before work starts. If your team uses another tool, we agree the delivery format at scoping.
Whichever the brief asks for; most engagements work inside an existing brand system, extending your type scale, colour tokens and components rather than reinventing them. Where guidelines are thin, we flag the gaps before starting. A ground-up identity is its own service, and we'll say so if a refresh is what you need.
From the blog
Design notes,
no filler.
The range
What it costs,
at the direct rate.
Each design discipline is priced on its own row below; this row is for buyers who want one standing senior design team across several of them, billed monthly.
- RetainerDesign team$4K–$10Kper month
Indicative: every figure is refined into an itemised proposal.INR figures shown excl. GST.
Put senior designers
on your next release.
A scoped, itemised design proposal. Your materials remain yours. Bespoke deliverable rights, licences and handover are agreed before work starts.
Reply within four business hours (typical) · NDA standard · Clear IP & Ownership Terms
Last updated