01 · Factory-line configurator · Schreiber Foods · 2026
Green Bay Machinery
A factory-line configurator helping sales engineers quote complete production lines faster, with every machine checked as they choose it.
Read the case study · password ›Siddhartha Roy Kanchala · Senior Product Designer
I make complex
products feel clear
Five years across enterprise, agentic AI, healthcare, finance and e-commerce. I stay with a problem from the first interview to launch.
PreviouslySchreiber FoodsCX by DesignDexiportKnitsol
Selected work
All work ›
02 · 0-to-1 product · Agentic workflow · AND India · 2026
Boards
An agentic workflow helping a two-person newsroom make its YouTube videos, with a person approving every step that costs money or trust.
Read the case study · password ›
03 · Client journey redesign · CX by Design · 2025
CX by Design
A redesigned client journey helping a two-founder consultancy give every client the same clear, steady experience.
Read the case study · password ›Step inside
Two worlds I built.
Look closer.
MoNA · Personal · 2026
Now, a little about me
About
{{w}}
Software engineering at Greenwich, then human-centered design at Pace. Since then I've designed products in London, Hyderabad and New York, and I still build the front-end when it helps the team ship.
- 2026
- Schreiber Foods, Product Designer
- 2025
- CX by Design, Team lead and Product Designer
- 2023–25
- Dexiport, Product Designer and Front-end
- 2021–23
- Knitsol, Product Designer
A note before you go
Let's talk
If you're building something complicated and want it to feel simple, I'd like to hear about it. Tell me what your team is making and where it's getting stuck. I'll bring examples of how I've handled problems like it.
Sid
The first button copies my email. Open your mail app instead
Work
The work
Products I took from the first interview to launch.
01 · Factory-line configurator · Schreiber Foods · 2026
Green Bay Machinery
A factory-line configurator helping sales engineers quote complete production lines faster, with every machine checked as they choose it.
Read the case study · password ›02 · 0-to-1 product · Agentic workflow · AND India · 2026
Boards
An agentic workflow helping a two-person newsroom make its YouTube videos, with a person approving every step that costs money or trust.
Read the case study · password ›03 · Client journey redesign · CX by Design · 2025
CX by Design
A redesigned client journey helping a two-founder consultancy give every client the same clear, steady experience.
Read the case study · password ›Experiences
3D spaces I designed and built from scratch. Watch them move, then walk through them yourself.
Want the full story?
Some of my work is password protected. Ask me for the password, or for a walkthrough on a call.
About
Hi, I'm Sid
A product designer who trained as a software engineer. I design complicated systems for the people who have to use them every day.
- Based in
- New York
- Designing for
- Five years
- Studied
- Software engineering, then human-centered design
- Also
- Builds front-ends with React and AI agents
What I do
{{w}}
How I got here
From writing code to designing what it does.
I trained as a software engineer and moved into design. Four cities, three continents, and the same habit everywhere: start where the work happens.
2019London
Software engineering at Greenwich, then my first design job at Knitsol.
2023Hyderabad
Product design and front end for clinics, stores and newsrooms at Dexiport.
2024New York
A master’s in human-centered design, then client work at CX by Design.
2026Green Bay
Enterprise tools for factory lines at Schreiber Foods. Yes, the cheese.
How I work
01
Start where the work happens
Plant floors, newsrooms, client calls. Before I draw anything I sit with the people who will use it. CX by Design began with more than 25 interviews.
02
Find the clear version
One decision per screen, and the hard parts moved out of the way. The GBM configurator made quotes 65% faster because people stopped guessing.
03
Stay until it ships
I trained as an engineer, so I build the front-end when it helps. GBM went from design to working React in 15 days.
Experience
2026Schreiber FoodsProduct Designer, Global IT UXGreen Bay, WI
2025CX by DesignTeam lead and Product DesignerNew York
2023–25DexiportProduct Designer and Front-endHyderabad
2021–23KnitsolProduct DesignerLondon
2021University of GreenwichTeaching Assistant, HCILondon
Education
MS, Human-Centered DesignPace University, New York · 2024–25
BE, Software EngineeringUniversity of Greenwich, London · 2019–23
What I work with
FigmaFigJamFramerPrototypingUser interviewsUsability testingJourney mappingDesign systemsWCAG 2.1 AAReactNext.jsTypeScriptTailwindClaude CodeCursorv0
Beyond work
When I'm not designing, I'm travelling, taking photos or out on a long walk. A few frames from the last few years.
A note before you go
Let's talk
If you're building something complicated and want it to feel simple, I'd like to hear about it. Tell me what your team is making and where it's getting stuck. I'll bring examples of how I've handled problems like it.
Sid
The first button copies my email. Open your mail app instead
Client journey redesignClient project · 2025
Making a small firm feel like a big one
CX by Design is a two-founder customer experience consultancy in New York. I led a team of four to redesign its client journey, so every client gets the same clear, steady experience, with the same team and the same tools.
The project in 60 seconds
Business0founders, competing with much larger firms
Problem0points in a project where clients felt lost
Research0+people in interviews and testing
Solution0new tools or hires
Impact0 hof manual work saved per client, every week
01 · The problem
Clients loved the work. The experience around it was uneven.
One project manager passed every email, update and follow-up along by hand. So how a client felt depended on who had time that week. Clients told us the same story at three points in a project.
First 10 days
OverloadedToo many documents at once.
“Too much info upfront, [the client] overwhelmed.”Diana, founder
10 weeks in
In the darkClients couldn't see their own progress.
“Clients see value when metrics are validated.”Lis, founder
After the project
ForgottenNo follow-up, and no reason to come back.
“No structured post-project engagement.”Our audit
Our question
How might we give every client the same clear experience, from the first email to long after the project ends, without adding admin work?
02 · Research
We studied bigger firms, then talked to everyone inside.
We compared six larger consultancies to see what clients expect. Then we ran 25+ interviews.
Lis and Diana, the foundersReal clientsCecil, a persona from client stories, when a client wasn't freeThe firm's teams, in sales, operations and content
What clients need at each stage, compared with CX by Design and four competitors. Very detailed reports overwhelm clients, so we kept the dashboard to a few numbers.
Our audit of the client journey at 10 days, 10 weeks and 10 months.
What we found
Four problems kept coming up.
We mind-mapped every interview and grouped the notes into themes. These four came up again and again.
01Nothing was connected.
The three tools didn't share information, so people copied it by hand.
02Every update sounded different.
Tone and timing depended on who wrote it that week.
03Clients couldn't see their progress.
It lived in tools only the team could open.
04Nothing happened after the project.
No follow-up, no feedback, no referrals.
+1And one rule: don't add people.
Every answer had to work with the same small team.
03 · The idea
They didn't need more people. Their tools needed to talk to each other.
HubSpot handled sales, Asana handled tasks and MailerLite handled email. We connected them, so updates move on their own and the project manager can focus on decisions.
Project manager
Founders
Client
Delivery team
HubSpot
Asana
MailerLite
Before · one person copies every update by handAfter · the tools pass updates to each other
What we chose, and what we didn't
Connect the three tools they already use
Hire more people, or switch software. Too expensive, and it meant retraining everyone.
A short dashboard and a weekly email
A long report. It overwhelms clients, and a small team can't keep it up.
04 · Iteration
Our first version broke our own rule, so we threw it out.
The first journey map needed new software, which was exactly what we promised to avoid. We rebuilt it twice.
“Iterate gradually. Refine one variable at a time.”Lis and Diana, founders
Organised by team, or by what the client experiences?
Drag to compare. The team view showed who owned each task, but not what the client went through.
05 · The solution
Automate the routine. Keep people for what matters.
How it fits together: one project manager, supported by three connected tools.
From a messy audit……to one continuous journey.
Every step now has a trigger, something that happens on its own, and a moment for a person.
ContractKickoff starts itself
- Trigger
- Contract signed in HubSpot
- Automatic
- Asana project and first tasks
- Person
- A personal note from Lis
10 daysOnboarding
- Trigger
- First Asana tasks begin
- Automatic
- Welcome emails, paced
- Person
- An intro video from Diana
10 weeksWorking together
- Trigger
- Task progress in Asana
- Automatic
- Dashboard and weekly email
- Person
- Progress explained in plain words
10 monthsReview
- Trigger
- Project moves to review
- Automatic
- Invite to book the review call
- Person
- Lis leads the review
AfterStaying in touch
- Trigger
- Project closes
- Automatic
- Added to the alumni list
- Person
- A thank-you note or case study
Happens automatically
- Onboarding starts when the contract is signed
- Tasks and deadlines are set up
- Welcome email and reminders
- Alumni and referral emails
Done by a person
- The story behind each update
- Conversations about risks
- The midpoint review call
- Final recommendations
Contract signed in HubSpotProject created in Asana, welcome email sends
Task completed in AsanaThe client dashboard updates
Milestone coming upReview-call reminder goes out
Project closedClient joins the alumni list
What testing changed
1
The checklist moved above the button.
People wanted to see the next steps before being asked to click.
2
Every step says what's next, and why.
Short notes that reduce confusion in the first 10 days.
3
One voice, signed by the founders.
Friendly but confident, from a shared tone guide.
4
It sends the moment the contract is signed.
So the first message lands while the excitement is fresh.
06 · The dashboard
One page that answers “where are we?” before anyone asks.
I designed the client dashboard. Clients and the team see the same status, so nobody has to write it up by hand.
Top rowReadable in 10 seconds.
Made for a busy founder, not a project manager. The first row answers the only question that matters: are we on track?
Middle rowStatus you can feel.
Colour shows the state before you read a word: on track, at risk, or blocked.
Weekly tableA story, not a spreadsheet.
Each week shows what was delivered, with a short note on why it matters. Clients can reply or rate it right there.
What testing changed.
Every round had at least 12 people. Three things they said shaped the redesign.
Where am I?
A clear current phase, so you always know where the project stands.
Is this good or bad?
Colour-coded status and milestone markers.
It reads like a report.
Plain, human notes, written for a person.
By phase: open any stage to see what happened each week.
Then I connected it to the real work.
I built a link that pulls task data from Asana into the dashboard, so it updates from the source and client updates take almost no effort.
Asana tasksClient dashboard
And one screen for the project manager.
Every client, the few checks automation leaves to a person, the sales pipeline and the running automations, in one place.
07 · Impact
Same team, same tools, a better experience.
0hof manual work saved per client, every week. No new hires and no new software.
First 10 days10 weeks inAfter the project
Before
OverloadedToo much at onceIn the darkProgress hiddenForgottenNo follow-upAfter
Clear next stepsWelcome email and checklistSees progressDashboard and weekly emailStays in touchAlumni emails08 · What I learned
What I learned, and what's next.
Check your work against your own rules.
Our first map quietly added new tools. Catching that was our best decision.
Connecting teams means translating.
Sales thinks in pipeline stages. Clients think in weeks. One shared map helped both.
A dashboard should end questions.
If a client still has to ask “where are we?”, the dashboard hasn't done its job.
Leading means deciding.
Each week I chose what we'd test and what we'd drop.
Next: a live link between Asana and the dashboard, and tracking how many weekly emails lead to a dashboard visit.
Thanks for reading.
That was CX by Design. Here's where to go next.
Personal · 3D, sound, storyMoNA · 2026
A museum that charges you to look
MoNA, the Museum of No Assets. A parody of dead NFTs and a monument to internet history. Five minutes, narrated by a hologram, and you leave with a Certificate of Nothing. I designed, built and scored it alone.
Start here: the film shows the whole visit in 75 seconds. Then walk through it yourself.Enter the museum ↗
5:00one visit, start to certificate
0 MBthe whole building, streamed
0lines for Augustus, the docent
0instruments in a score that decays
0launch posters
Solodesign, 3D, code, sound, film
01 · The joke
The building is free. Your attention is the fee.
NFTs sold the idea of owning something you could only look at. MoNA turns that around: you own nothing, and looking is what costs. It started as a virtual-museum assignment in a human-centered design class. The class ended. The idea didn't.
Your wallet, as you scroll
300coins. One a second.
Every visitor starts with 300 coins and spends one each second inside. As the wallet empties, the music falls apart and the docent starts to fade.
02 · The collection
Masterpieces of the recent past.
Every work is a type of NFT the internet already forgot, hung in a gilt frame and labelled like a treasure.
03 · Augustus
A hologram of a drawing of a sculpture.
Your docent has 62 lines and a leitmotif, and he glitches as your wallet drains. Press play to hear him.
04 · The building
Neoclassical, procedural, 12 MB.
A colonnade, a drum, a saucer dome and a vaulted gallery, modelled in Blender with Poly Haven scans, lit and baked in Cycles, then streamed into three.js as one 12 MB file.
Real renders from the museum. Quality adapts to the visitor's computer and never drops below full resolution.
Look around
Walk around the building, right here.
The real building, the real art, Augustus at the centre. Walk through it yourself.
Explore in 3DOpens the museum · about five minutes
05 · Sound
An orchestra that falls apart with your money.
The score composes itself from a soundfont of 11 instruments and decays as the coins run out.
The cracked fanfareFor the entrance.
The ragFor the galleries.
The sad tromboneFor the empty wallet.
The hold musicFor when you run out.
The visit, on a phone
Admit one. Look. Leave with proof of nothing.
The share loop
The Certificate of Nothing.
Every visitor leaves with a certificate in their own name, recording exactly how much time they spent looking at nothing. It's the souvenir, the punchline and the reason people share it.
Launch
19 posters, in the museum's voice.
A launch campaign that never breaks character.
06 · What I learned, and what's next
One thesis, carried through every detail.
A joke needs a system.
“Attention is the fee” decided the wallet, the music, the docent and the ending.
Ship the whole thing.
Design, 3D, code, voice, score, film and posters, by one person.
Next.
Lightmaps, post-processing and a VR version.
Made with Blender, three.js, Poly Haven (CC0), the FluidR3 soundfont, Piper voice (MIT) and open-licensed fonts.
Next project
Therapod
A room that breathes with you ›Product and service designTherapod · a concept for 2040
A room that breathes with you
Therapod listens to your body, learns what calms you, and keeps you steady through the weeks before care. Mental clarity, made tangible.
What Therapod sees.Breath, heart and the warmth of her hands. Never a face. Nothing leaves the room.Breathing at six a minute
The launch film shows one session, start to finish. Then step into the room yourself.Enter the room ↗
0semi-structured interviews
0 daysmedian wait for a first psychiatry visit
4 → 1senses, paced by one breath rhythm
0 bytesof raw signal kept, by design
The 60-second version
Help is weeks away. Therapod is there tonight.
Problem
When someone finally asks for help, the first appointment is often weeks away. Those weeks are lived alone, and the apps people try are dropped fast.
Insight
In 12 interviews people asked for quiet, not advice, and senses, not screens. They wanted to feel understood without feeling watched.
Solution
A device that reads breath, heart and warmth, learns what calms you, and paces light, sound, scent and touch to one rhythm.
My part
End to end: research, the device, the service blueprint, the brand, the app, the films and a working 3D build.
01 · The problem
Help is weeks away. The stress isn't.
Deciding to get help is hard. Then comes the wait. For weeks, people carry it alone at home.
She asks for helpThe wait · a median 67 days · where Therapod sitsCare begins
19.5% → 26.6%US adults 18–29 with anxiety symptoms, 2019 to 2022NCHS, 2024
18.5%of psychiatrists contacted offered a new patient an appointmentSun et al., 2023
137MAmericans live where there aren't enough mental health professionalsHRSA, 2025
3.9%of users a mental health app still has after 15 daysBaumel et al., 2019
02 · Research
Four themes, and one tension that became the brief.
Theme 1
Give me space, not advice. Quiet, not something talking at them.
Theme 2
Senses over screens. Sound, light and scent felt more comforting than another app.
Theme 3
Privacy and control first. They wanted to decide when and how they're helped.
Theme 4
Still, be understood. Something that gets their state without explaining it.
The tension · themes 3 and 4
Help people feel understood without ever feeling watched.
From the research board: the interview canvas. Below, the persona canvas that became Sophia, 28, six weeks from her first appointment.
03 · Concept
One device. Four senses. One rhythm.
Therapod sits on a console and turns the room into an 18-minute place to settle. Everything follows one breath rhythm, slowing towards six breaths a minute.
Reads the body, learns her, paces the room
- Breath, heart rate and skin warmth, plus a one-tap check-in
- The T1 engine learns her patterns on the device. Nothing goes to the cloud
- Up to 360° of light, sound, a matched scent and a pulse on every breath
04 · Evidence
Five decisions, each tested against research.
The first concept was built on what felt calming. I checked each idea against published studies and our interviews, kept what held up and changed what didn't.
01
Breathing became the core.
One therapy among four.
Every sense follows one breath rhythm, slowing to about six breaths a minute.Paced breathing with biofeedback cut stress and anxiety by a large margin across 24 studies. Goessl et al.
02
Sensing stays minimal.
Track as many signals as possible to infer mood.
Breathing, heart rate and warmth only. Her check-in outranks all of them.60% of Americans would be uncomfortable with a provider relying on AI for their care. Pew, 2023
03
It learns her, then steps back.
The same session for everyone, from a menu.
Pace, scene, scent, length and timing adapt to her. She can see, change or erase everything.The calmest breathing rate varies by person, so biofeedback is tuned to each one. Lehrer and Gevirtz, 2014
04
The senses must agree.
Any scent with any scene.
Every scene has a matched scent, and each sense switches off on its own.A mismatched scent made relaxation worse. Max Planck, 2025; Lopes, 2024
05
One score, never a grade.
No feedback, so no reason to come back.
One calm score per session and three readings. No streaks, no comparisons.Guilt-driven streaks make leaving feel like failing.
05 · One evening
9:40 pm. Eighteen minutes.
What Sophia sees, and what Therapod is doing. The app is the quietest part: used before and after, never during.
9:40Arrive
Wired. Shoulders up since noon.
One tap to begin. The amber light on the band shows the sensors are on, and they can be switched off.
9:41Check-in
Heard, without having to explain.
One question, one tap. Her answer outranks every sensor and sets the starting pace.
9:44Settle
I can put the phone down.
The phone goes dark. The ring paces her breath from 14 a minute towards 10.
9:50Immerse
Shoulders drop.
Light wraps the walls and dims around her eyes. Breath settles near six a minute.
9:58Close
Lighter.
Light fades over 60 seconds. A floating summary, then her own answer. Raw signals are erased.
06 · It learns you
It gets better at being hers.
Week 1Getting to know her
Starts from her check-in. Notes how fast her breathing slows and which scene she lets run.
Week 2Finding her pace
Lavender didn't help, so it tries cedar with Snow Peaks, and her score climbs.
Week 5A step ahead
Weeknights from 9 to 10 are hardest, so it offers a session at 9:30.
What it learns
- When she tends to be tense
- How long she takes to settle
- The scenes, scents and sound that help
- Her own words from each check-in
What it never learns
- Anyone else in the room
- Her voice, her image or her location
- Anything outside a session
- Anything she has switched off or erased
07 · Service
A service, not a gadget.
A device, an app, rules about data, and a hand-off to people when it matters. The blueprint shows where trust has to be made visible on purpose.
Every failure has a designed recovery.
The sensors misread her
It doesn’t get me.Her check-in wins, and one tap corrects the reading.
She turns the sensors off
Will it work worse?A full session runs on the check-in and the breath ring.
Someone walks in
This is awkward.A shared session: no personal sensing, nothing kept.
She wants to stop
I’m done.Stop ends everything within 2 seconds. No “are you sure?”
Offline or a power cut
Did it break?Breath and sound run locally on battery.
She stops using it
…No guilt notifications. One gentle note after 14 days, then quiet.
When it's more than stress, Therapod doesn't pretend.
TriggerHer own words, or a pattern she opted into. Never a sensor alone.
PauseThe session stops. The room stays softly lit.
Offer, never forceHer trusted person, her therapist, or 988.
“Not now” is respectedNo nagging. Options stay one tap away.
Nothing shared automaticallyEvery contact needs her tap.
08 · The app, brand and launch
Calm is a pace.
Everything moves at six breaths a minute, four seconds in and six out: the mark, the motion, the sound and the film. The 2040 app is the quietest part of it.
The box is the first breath: soft-touch black with one ring printed in luminous ink.
09 · Reflection
A speculative concept, held to real standards.
Not tested with users, and not a medical device. Every reading shown is simulated. Success would mean people feeling steadier during the wait, and more of them making it to that first appointment.
Designing for emotion is designing for control.
The sensor light, the check-in that wins and “erase everything” matter more than any feature.
Find the moment that matters.
The device got clearer once it had a job: the weeks between asking for help and getting it.
Evidence sharpens a concept.
Cutting the weakest claims made the product more honest and more focused.
Speculative design still owes people safety.
The escalation path took more care than any screen.
Team: Divya Boni, Falguni and Siddhartha Roy Kanchala. With NYDF and the Seidenberg School. Made with Figma, Miro, Blender and Three.js.
Next project
CX by Design
Every update ran through one person ›Green Bay Machinery
This case study shows work I did at Schreiber Foods, so it's password protected. Enter the password to read it.
That's not it. Ask me for the password.
Don't have it? Ask me by email
Product designSchreiber Foods · 2026
Building a factory line, one decision at a time
GBM (Green Bay Machinery) builds food production lines. Before a customer gets a price, a sales engineer has to choose machines that all work together. I designed a guided configurator that checks every choice as it's made.
The company
Schreiber Foods makes the cheese inside some of the world's biggest food brands.
An employee-owned dairy company based in Green Bay, Wisconsin. Its cheese slices are used by 17 of the top 20 hamburger chains. I designed this configurator on its Global IT UX team.
$0B+in annual sales
0,000+people worldwide
0plants in 11 countries
Source: Schreiber Foods company profile.
The project in 60 seconds
Line0machines that all have to work together
Flow0guided steps, from context to quote
Accuracy0%more accurate configurations
Build0 daysto build the front end
Impact0%faster quote turnaround
01 · The problem
Every machine on a line depends on the one before it.
A line runs from the cooker to the palletizer. If one machine can't keep up, everything after it slows down. Sales engineers had to get every choice right by hand before a customer could get a price.
What had to be right
Four questions behind every quote.
01Will each machine keep up?
Every machine has to match the line's target output.
02Where will the line slow down?
One slow machine holds back everything after it.
03Does it meet the rules for this market?
Local, retail and export lines follow different safety standards.
04Is it worth the money?
Customers want to know what a line will save before they commit.
02 · The approach
Answer the big questions first, then go one machine at a time.
I started with a UX audit of how lines were being configured. It led to one idea: set the context up front, then guide the engineer through the line in the order it runs, checking each choice as it's made.
The first screen asks four questions. The answers decide which machines are valid later.
03 · The flow
Eight steps, in the order the line runs.
ContextSet the rules first.
Region, target output, safety level and product type. Every later choice is checked against these four answers.
Step 1 · CookerPick a machine, see the impact.
Each model shows how well it meets the target. If it falls short, it says so and suggests a fix.
Step 4 · CheckweigherGreen means it keeps up.
The line builds itself on the right as you go, with each machine and its yearly cost.
Step 5 · Flow wrapperThe slow machine is named.
The bar at the bottom shows line speed against the target, and which machine is holding it back.
Step 7 · PalletizerThe whole line, at a glance.
By the last machine, the preview shows all seven, with efficiency and estimated return.
SummaryReview, then send for pricing.
An equipment list, projected savings, and one button that sends it to engineering.
04 · The details
Every screen answers “is this line going to work?”
Right panelThe line builds itself as you go.
Each machine appears in order with its yearly cost. Efficiency and estimated return update with every choice.
Each machineA problem comes with a fix.
If a machine falls short, it shows by how much, says an upgrade is needed, and offers a fix in one tap.
Bottom barThe slow machine always has a name.
Line speed against the target, and the machine slowing the line, stay on screen at every step.
05 · Sending it
Save a draft, or send it for an official quote.
Engineers can save a configuration and come back to it later. When it's ready, one short form sends it to engineering for a formal quote and technical drawings.
- Saved as a draft until it's sent
- Status history shows where each request is
- Reviewed within 24 hours by the engineering team
06 · Impact
Faster quotes, with fewer mistakes.
0%faster quote turnaround
0%more accurate configurations
0days to build the front end
07 · What I learned
What I learned.
Ask the hard question first.
Setting the context up front removed choices that could never have worked.
Show the consequence, not just the option.
Efficiency and the bottleneck bar make the effect of every choice visible straight away.
Keep the specs in sight.
Capacities and specs stay on screen, because that's what sales engineers trust.
Thanks for reading.
That was Green Bay Machinery. Here's where to go next.
Boards
This work is under NDA, so it's password protected. Enter the password to see it.
That's not it. Ask me for the password.
Don't have it? Ask me by email
Boards
Software that does a newsroom's slow video production work for AND India, with a person deciding every step that costs money or trust. In daily use since 12 October: 50K+ views and 1,500+ watch hours in its first week.
Both open in a new tab.
Clayra
This work is under NDA, so it's password protected. Enter the password to see it.
That's not it. Ask me for the password.
Don't have it? Ask me by email
Clayra
A premium Indian kitchenware brand made in clay and wood. I shaped the brand and designed a mobile-first storefront that shows shoppers only what they need next. 29% more mobile conversion.
This one is under NDA, so I walk through it live, screen by screen.
CX by Design
This case study is password protected. Enter the password to read it.
That's not it. Ask me for the password.
Don't have it? Ask me by email
Clinicvize
This work is under NDA, so it's password protected. Enter the password to see it.
That's not it. Ask me for the password.
Don't have it? Ask me by email
Clinicvize
A 0-to-1 operating system for clinics, designed for four kinds of staff in one product. Four clinics took it on within 100 days.
This one is under NDA, so I walk through it live, screen by screen.