Founders who need to show the idea first
Investors keep asking what it looks like, and all I have is a deck.
We turn your notes and sketches into a clickable prototype for investor meetings and user tests, before anyone writes code.
UI/UX design
Product design for SaaS and startups, clickable before it's built
A flow map first, then a clickable prototype you can try on your phone.
- Files in your Figma organization
- Design only, or design and build
- Prototypes you can test with users
30 minutes with a founder. Times show in your time zone.
UI/UX design at a glance
UI/UX design services for SaaS and startups: user flows, UX audits, and clickable prototypes in your own Figma. Design only, or design and build together.
- Who it’s for
- Founders who need to show the idea first
- SaaS teams losing people between sign-up and paid
- Startups adding features faster than they design them
- What we build
- Product design for web and mobile apps
- SaaS onboarding and UX audits
- Clickable prototypes for investors and first users
- Design systems
- Built with
- Figma
- Figma Dev Mode
- GA4, Mixpanel, or PostHog, plus Microsoft Clarity
- Maze
- A shared Slack channel with our team
- What you own
- Code in your GitHub from day one
- Cloud and store accounts in your name
- IP assigned as each invoice is paid
How we'd run yours
Example plan
We don't have public case studies yet. Here's how we'd run an onboarding audit and redesign for a seed-stage SaaS whose 14-day trials rarely convert.
- Kickoff
Your users, activation event, and trial data. We sign up as a new user and map each step, with drop-offs marked.
- Audit
Each issue with a screenshot, severity, and fix, split into quick wins and redesign work, and walked through with you.
- Wireframes
Gray-box wireframes: fewer fields, sample data, and one clear first action. You click through them.
- Visual design
Visual design in your brand, with every state, as a clickable prototype of the new trial.
- User tests
Video tests with target users. We fix where they get stuck.
- Handoff
Final screens, a starter UI kit, Dev Mode specs, and a walkthrough with your developers or ours.
This is an example plan, not a past client project.
Who this is for
Sound familiar?
SaaS teams losing people between sign-up and paid
Trials start, then stall. We can’t tell which screen loses them.
We find where people drop off in onboarding and checkout, rank the fixes, and redesign the screens that matter most.
Startups adding features faster than they design them
Every new screen looks different, and developers keep asking which button to use.
We set up a design system in Figma, with components named the way your code names them.
What we build
Product design for web and mobile apps
We design SaaS products, web apps, and mobile apps. Flows and gray-box wireframes come first, so we agree on how it works before we pick colors. Then visual design for phone and desktop, with every state: empty, loading, error, and first use. Your developers get a clean Figma file with specs and a walkthrough call.
SaaS onboarding and UX audits
Live, but trials stall or carts get abandoned? We go through sign-up, onboarding, and checkout as a new user, and read your funnels and recordings. Each problem comes with a screenshot, its severity, and a fix. Quick wins are listed apart from redesign work, so your developers can start the next day. We won't propose a full redesign when three screens are the problem.
- Trial-to-paid and checkout drop-off
- Onboarding teardown before a launch
- Product built without a designer
Clickable prototypes for investors and first users
We turn your notes, sketches, or screenshots of apps you like into a Figma prototype that clicks like a real product. Use it in user interviews, or walk an investor through it on your phone. It doubles as a spec for build estimates. It has no working code or real data. For that, see MVP development.
- Investor demo prototype
- Prototype as a build spec
Design systems
Colors, type, spacing, and components like buttons, forms, and tables, built in Figma and named the way your code names them. Small teams start with a light UI kit, not a 100-page manual. New screens look like they belong, and developers stop guessing.
- Starter UI kit
- Cleanup of a messy Figma file
- Components matched to your front-end code
How a project runs
Plain English at every step, and calls set around your working day.
How we start
We start with your users, goals, and any brand you have. The Figma project sits in your organization. If we also build, the GitHub repository and cloud accounts are in your name from day one. IP is assigned to you as each invoice is paid. First up: a flow map of every screen in scope.
Working together
You try the work on your phone and comment on the screens. AI drafts; a named designer reviews every screen, and a named engineer reviews every code change. We price by the project or the week, so faster work doesn't raise your bill.
A board you can open
The shared board shows each screen as in design, waiting on you, or approved. You get written updates and a preview link as the work moves. See how we work.
Who you talk to
There's no account manager in between. Our team is in India, and we set call times around your working day.
Stack, and why
Figma
Design, prototypes, and handoff, in your organization. Viewing and commenting are free.
Figma Dev Mode
Exact sizes, colors, and spacing for your developers.
GA4, Mixpanel, or PostHog, plus Microsoft Clarity
For audits: funnels and session recordings, in your own accounts.
Maze
Remote prototype tests with your target users.
A shared Slack channel with our team
Questions, screen links, and decisions in one place.
GitHub repository in your name
If we also build, code lives in your GitHub from day one.
Questions founders ask
Straight answers, including the ones about cost and time.
Can you design it and let our developers build it?
Yes. Design only, or design and build with the same team. We hand off a clean Figma file with specs and walk your developers through it.
What is a UX audit?
A UX audit is a structured review of an existing product to find where users get stuck: unclear steps, confusing screens, and drop-off points. You get what we found, ranked by impact, and what we would change first.
What is a clickable prototype?
A clickable prototype is a set of designed screens linked together, so you can tap through the product on a phone or in a browser before any code exists. It lets you test the idea with users and show it to investors or developers.
What's the difference between a clickable prototype and an MVP?
A prototype looks and clicks like your product, but nothing behind it works: no accounts, data, or payments. An MVP is working software that customers sign up for and pay for.
What is a design system?
A design system is a shared set of colors, type, spacing, and components, like buttons, forms, and tables, that every screen is built from. It keeps new screens consistent and saves developers from guessing.
Will a clickable prototype help us raise money?
It lets investors see the product instead of imagining it, and shows you've tested the flow with users. It won't replace traction. We design the few screens that tell your story, not every screen.
What does a SaaS onboarding UX audit need from us?
A test account, your analytics or session recordings if you have them, and your activation event: the action that shows a new user got value. No data yet? We audit as a new user and say where the evidence is thin.
How much does UI/UX design cost?
It depends on how many flows and screens are in scope, and whether it's an audit, a prototype, or a design system. On the call, you get a ballpark range. After scoping, you get a written estimate. We price by the project or the week, never by the hour.
Who owns the designs, code, and IP?
You do. Figma files sit in your organization, and code lives in your GitHub from day one. IP is assigned to you as each invoice is paid. Editing in Figma needs a paid seat on your side.
What hours do you work?
Our team is in India. We set call times around your working day, wherever you are, and questions go in a shared Slack channel.
Show us the idea, or the screen where users get stuck.
Or tell us which one sounds like you:
Or put it in writing
A few lines are enough to start, and nothing here commits you to anything.
- Tell us what you’re building.Who it’s for, what it needs to do, and any deadline you’re working to.
- A founder reads it.You get a reply by email, usually with a couple of questions.
- We talk for 30 minutes.You leave with a ballpark range, and a straight answer if we’re not the right fit.
Prefer email? sales.bydtech@gmail.com.
Send a briefGoes straight to the founders. No newsletter, no CRM sequence.