llms.txt
Compare with other sites' llms.txt files →# Studio Maydit
> Studio Maydit designs websites and products for tech companies that are about to launch, just raised, or done settling for design that doesn't match what they built.
Studio Maydit is a design partner for tech companies. It designs and builds websites and products for AI and B2B software companies that need senior design without building an in-house team, usually right before a launch or just after a raise.
- Website: https://studiomaydit.com/
- Book an intro call: https://cal.com/maydit/45min
- Email: hello@studiomaydit.com
- Profiles: https://clutch.co/profile/studio-maydit, https://www.linkedin.com/company/studio-maydit, https://x.com/heysidoku, https://www.framer.com/@studio-maydit
## Services
- **Product Design**: End-to-end product design: research, flows, and interface systems that turn a complicated product into something people use without thinking about it. Includes UX research, AI MVP design, mobile app design, web app design, interaction design, and design systems.
- **Website Design**: Websites that make funded AI and B2B software companies look as good as what they built, shaped around your story and designed to turn visits into booked demos. Includes landing pages, website redesign, brand direction, copy and messaging, motion and illustration, and design systems.
- **Website Development**: Pixel-perfect builds in Framer, Webflow, or custom code (Next.js), shipped in weeks with CMS, SEO, and performance handled so your team can publish on day one.
## Case studies
- [SATHI: Launch website for affiliate SaaS from the team behind $59M+ in influencer sales](https://studiomaydit.com/work/sathi): How Studio Maydit designed the launch site for SATHI, the new affiliate platform from SARAL: a mythology-rooted website in a category of black-and-blue SaaS sites, live in 7 weeks with 5,000+ visits in launch week.
- [Chariot: Website and public launch for one of India’s four government-backed AI labs](https://studiomaydit.com/work/chariot): How Studio Maydit designed and built the public launch site for Chariot, one of four teams selected under the IndiaAI Mission to build India’s foundation models, from kickoff to launch in 7 weeks.
- [Mi-VAD: Website for a health-tech company building a heart pump with Mayo Clinic and Cornell experts](https://studiomaydit.com/work/mi-vad): How Studio Maydit designed and built the Mi-VAD website in Webflow: quiet, investor-facing design for a 12.7-gram heart pump invented by Mayo Clinic’s cardiac transplant director, live in 9 weeks.
- [Dualite: Designing the website and product behind Dualite’s 100k user signups](https://studiomaydit.com/work/dualite): How Studio Maydit led brand direction, designed and built the website and redesigned the product for Dualite, the 100X.VC-backed AI app builder used by 100,000+ people in 150+ countries.
- [Green Glass: A wine app that learns your taste, designed and launched in 90 days](https://studiomaydit.com/work/green-glass): How Studio Maydit designed the Green Glass iOS app and designed and built sipgreenglass.com for a wine app that learns your taste, kickoff to launch in 90 days.
- [Syncrodesk: Designing one secure workspace that replaces a dozen tools for regulated teams](https://studiomaydit.com/work/syncrodesk): How Studio Maydit designed Syncrodesk’s website and product: one secure workspace for CRM, meetings and HR, eight CRM modules end to end, built to serve engineering, healthcare, retail and education teams without breaking consistency.
- [Sawdust: Brand licensing website for a music tech company used by Skrillex and Hardwell](https://studiomaydit.com/work/sawdust-website): How Studio Maydit designed and built the Sawdust website: a landing page that lets brands hear original underground electronic music and makes licensing it feel simple.
## Frequently asked questions
### Is this a fit
**We're talking to a few agencies. Why Maydit?**
One team designs your website and product, so both tell the same story. The scope is fixed after week 1, so the plan doesn't move under you. And it shows in the results: Dualite saw a better impressions-to-signup ratio after its new site.
**We're not an AI company. Is that still a fit?**
Yes, if your product is complex and your buyer isn't technical. Making that kind of product easy to understand is the work we do, whatever the industry.
**Who do you usually work with?**
Mostly AI and B2B software companies that have outgrown their design: a site that no longer explains what they do, a product people sign up for but do not stick with, or a launch coming faster than their team can design for. They need senior design without building an in-house team.
**What do you help with, exactly?**
Websites and products. For websites: positioning, copy, design, and a Framer, Webflow, or code build that turns visits into demos and signups. For products: research, flows, UI, and a design system, so users get value sooner and engineers have clear designs to build from.
**Do you only work with AI companies?**
Most of our clients are AI or B2B software companies, so that is where we have the most experience. We also work with other technical products that are hard to explain, using the same process.
**Who is actually doing the work?**
A senior designer, assigned from day one, works on your project with Sid, our design lead, who you meet on the discovery call. You talk to both of them directly in Slack and on reviews, and the same people stay with your project from start to finish.
**Can we see work similar to ours?**
Start with the case studies on the site. On the intro call we will walk you through the projects closest to yours, including some we cannot publish yet.
**We have been burned by an agency before. What is different here?**
You work directly with the designers on your project, and you can see progress in Slack and Figma as it happens. At the end of every project, we also give you a written note on what is working well and what we would improve next.
**Why not just hire our own designer?**
Hiring can be the right call once design is a constant need. Until then, one person rarely covers brand, website, product, and build, and a senior hire can take months to find. We cover all of these from the start, and you can scale us up or down as your roadmap changes.
**Why not just use AI tools to design it ourselves?**
AI tools are useful, and we use them every day. They are good at producing layouts quickly. The harder part is deciding what your product should say, who it is for, and what will make people trust it, and that is where most of our time goes.
**Is it too early for us if we are pre-product?**
It depends. If you are still deciding what to build, an intro call will help us both see whether design is the right next step. Teams usually get the most from us once they have something concrete: funding, a launch date, or a working MVP that needs better design.
**When are we not a good fit?**
When the scope is still moving but only a fixed price will work, when you need a full naming and identity programme, or when you need your product's code written. We will say so on the first call and point you somewhere better.
### What we do
**What is actually included in a website project?**
Usually a homepage, pricing, about, and feature pages, each built to move the right visitor toward a demo or trial, plus landing pages or a component library if you need them. We agree the page list before we start.
**Do you build the site too, or just design it?**
Both. We build marketing sites in Framer, Webflow, or custom code, with the CMS, SEO, and performance set up, so your team can publish updates on their own from launch day.
**Do you write the copy as well?**
Yes, with you. We shape the story and write the headlines and sections, and you bring the facts only your team knows. The words are settled before we design each section, so the layout fits what you need to say.
**Can you design a product from a blank page?**
Yes. We regularly take an idea with nothing built yet through research, user flows, and UI, and hand over a design system your engineers can build from directly.
**Can you fix something that was vibe-coded or built with AI?**
Yes, it is a common starting point for us. We find where people get confused or stuck, tighten the structure so the core actions are clear, bring the visuals into one system, and hand back clean files with notes on what still needs work.
**Do you write the code for our product?**
No. We design the product and work closely with your engineers while they build it, with design reviews so what ships matches what was designed. If you do not have engineers yet, we can introduce you to development partners we trust.
**Do you design for mobile apps too?**
Yes. Product work covers web and mobile apps, including onboarding, empty states, and error states, which have a big effect on whether people keep using an app.
**Can you work inside our existing design system?**
Yes. If you have one, we extend it and keep it consistent. If you do not, we build one in Figma so your team can ship new pages and features without starting over each time.
**Do you handle branding?**
We shape brand direction rather than a full identity programme from zero: the type, colour, imagery, and motion that make your site and product feel like one company. If you need naming and a complete identity system, we will say so and point you somewhere better suited.
**Do you do user research and usability testing?**
Yes, sized to what the project needs. That can be a review of your analytics and session recordings, interviews with a few users, or testing a prototype before anything is built. Testing early helps us find confusing flows before launch.
**Can you do motion and interactions?**
Yes. We plan motion as part of the page design and build it in Framer, Webflow, or code. If an idea needs a specialist 3D or WebGL studio, we will tell you at the start.
**How many design directions will we see?**
A few in the early stage, so you can react to real options. We then narrow them down to one with you before designing the full pages or screens.
**Do you design pages to be accessible?**
Yes. We check contrast, type sizes, focus states, and keyboard and screen reader basics as part of the normal design and build.
**Which tools do you work in?**
Figma for design and prototypes, Slack for day-to-day conversation, and Framer, Webflow, or Next.js for builds. If your team lives in other tools for tickets or docs, we work in those too.
### Pricing and payment
**How much does a project cost?**
It depends on scope: a fixed price for a defined project, or a monthly retainer for ongoing work. Book an intro call and we will send a clear quote after hearing what you need.
**Can you work within a fixed budget?**
Yes. Share your budget on the intro call and we will tell you what fits within it. If it cannot cover what you need, we will say so and suggest what to prioritise.
**Should we pick fixed scope or a retainer?**
Fixed scope suits work with a clear end point, such as a website, a launch page, or a defined set of screens. A retainer suits design that needs to keep pace with a roadmap that keeps changing.
**Do you charge by the hour?**
No. Work is priced by scope or by month, and you know the price before work starts.
**How does the retainer work?**
You get design every month: new pages, campaigns, product screens, or the system behind them. We work through one active task at a time, ship it, then move to the next, and we can join your team's channels and rituals like part of the team.
**Why do you suggest a retainer for product work?**
Because products change while you build them. It is hard to know every screen before the first user test, so a fixed quote either needs a buffer or a new quote for each change. A retainer lets the design work follow your roadmap instead.
**How do we know a month on retainer was worth it?**
You see what shipped each week, and at the end of each month you get a short written summary of what got done and what is next. If you want to change the scope, pause, or stop, you can.
**Can we start with something small first?**
Yes. A single landing page, an audit, or one core flow is a good way to see how we work before committing to more. Plenty of longer partnerships started that way.
**Can we pause or cancel later?**
Yes. You can pause, change the scope, or cancel, and there is no long lock-in.
**How does payment work?**
Fixed projects are paid in parts: some upfront to start, the rest at agreed milestones or on completion. Retainers are billed monthly in advance. Everything is agreed in writing before work starts.
**Who pays for hosting, fonts, and other tools?**
You do, on your own accounts, so everything stays yours after we finish. That covers the Framer or Webflow plan, hosting, domains, and any paid fonts or stock. We set it all up and tell you what each one costs before you commit.
**What do you need from us to get a quote?**
An intro call, access to whatever exists already, and one person on your side who can make decisions. Everything else we can pull together as we go.
### Timelines
**How long does it take?**
It depends on what we are making. A landing page or homepage takes two to three weeks, and a full marketing site four to six. A focused product or AI MVP takes two to three weeks, and a design system four to eight. Building finished designs takes two to four weeks in Framer or Webflow, or three to six in custom code. If you have a hard date, we plan back from it in week 1.
**How long does a website take to build?**
A focused landing page or homepage usually takes two to three weeks. A full marketing site takes about four to six. Custom illustration, heavy motion, or a custom code build adds time, and we agree the timeline before we start.
**How long does product design take?**
It depends on how much there is. The core flows of a focused MVP usually come together in the first month, and a full platform runs longer, which is why bigger products work best on a retainer that keeps pace with engineering.
**How soon can you start?**
Usually within a week or two, depending on current projects. Ask on the intro call and we will give you a realistic start date.
**Can you work around a hard launch date?**
Yes, in most cases. Tell us the date on the intro call, whether it is a launch, a demo day, or a board meeting. If it is achievable, we will plan the scope around it. If it is not, we will tell you up front.
**Can we launch a smaller version first and do the full thing later?**
Yes, and it is often a good plan. We design the first version so it can grow into the next one, so you can launch sooner without redoing work later.
**Can development start before design is finished?**
Yes. Once a page or flow is signed off, your engineers can start on it while we design the next one, so design and build run side by side instead of one after the other.
**What if the scope changes partway through?**
We quote the new piece separately, so the original plan and timeline stay clear. You decide whether it goes in now or after launch.
**What usually causes delays?**
The most common causes are slow or scattered feedback, copy and content arriving late, and decisions waiting on someone who has not seen the work. Having one decision maker and keeping feedback in one place helps the most.
### How we work together
**How does a project kick off?**
With a working session on your product, your users, and where the business is heading. From there we share the plan for the first weeks, set up a shared Slack channel, and get to work.
**What does day-to-day communication look like?**
Mostly through Slack with regular check-ins, and everything happens in Figma where you can comment directly. You always know what is in progress and what ships next.
**How much of our time will this take?**
Usually a kickoff session, a weekly check-in, and someone who can give feedback within a day or two. Everything else happens in Slack and Figma, at a pace that suits you.
**What time zones do you cover?**
We work with teams in many time zones and mostly work async, so work keeps moving without everyone needing to be online at the same time. There is a window each day for live calls when you need one.
**Can we bring our own ideas and references?**
Yes, they help a lot. Sites you like, competitors, sketches, and screenshots are all useful, and we will tell you what we would take from each and why.
**How do you take feedback?**
You can comment directly on the designs in Figma or send notes in Slack. We collect it, ask about anything unclear, and share the next version. Feedback works best when it comes early, is specific, and comes from one decision maker.
**How many rounds of revisions do we get?**
Revisions are included within the agreed scope. They go fastest when feedback comes early and in one place, rather than all at the end.
**What if we do not like the direction?**
Tell us early, and be as specific as you can. We go back to the options, work out what is not working, and adjust before more is built on top of it. This is why we share directions before polished pages.
**What if we are not happy with the work?**
Tell us as soon as something feels off. It is much easier to change course early than at the end. If we still cannot get it right, we will tell you honestly and discuss what to do next.
### Working with your team
**Can you work alongside our developers?**
Yes, that is how most product work happens. We join your planning, answer questions as they come up, and review what gets built against the design, so small gaps get fixed before release instead of after.
**Can you work with our in-house designer or product manager?**
Yes. We fit around the people you already have, add capacity where it is needed, and leave your team with organized files and a clear system.
**Do you need access to our product, analytics, or code?**
Only what helps the work, and only with your permission: usually a test account, view access to analytics, and the current designs. We handle all of it with care, and we sign an NDA if you want one first.
**What do engineers get at handoff?**
Build-ready Figma files: organized pages, documented components, every state including the less obvious ones, and notes on behaviour, so your engineers can build with as few open questions as possible.
**Will you check that the build matches the design?**
Yes. We review what your team builds, point out where it differs from the design, and help decide what to fix now and what can wait.
### Ownership and confidentiality
**Will you sign an NDA?**
Yes. You can send yours before the intro call if you want to discuss details from the start.
**Who owns the files when we are done?**
You do. Figma files, the Framer or Webflow site, and any code move to your accounts, organized so another team could continue the work on their own.
**Do you use AI in your work?**
Yes, as a tool for exploring ideas, imagery, and prototypes, and for speeding up builds. Our designers make the decisions and review everything before it ships.
### After launch
**How do we know the new site or product is working?**
We agree what success looks like before we start: demo requests, signups, activation, or fewer support questions. After launch we look at those numbers with you and say what moved and what we would try next.
**Can our team edit the site after launch?**
Yes. We build in Framer or Webflow with CMS templates for your pages and posts, and record Loom walkthroughs for your team. You own every file and account.
**Do you take care of SEO and site speed?**
Yes. Metadata, page structure, redirects, and page speed are part of every build, so the site is easy to find and quick to load from launch.
**Do you fix bugs after launch?**
Yes. We run a round of fixes before handover, and if something we built is not working after launch, tell us and we