FAQ
Frequently asked questions
A few things you might want to know before we work together.
Hiring and working together
Yes. Vanya Studio is my independent design practice. I lead the work from the first conversation through delivery. I’m comfortable working alongside your founders, designers, engineers and marketing team, or joining a project through another studio. If we need a specialist, I’ll discuss their role with you up front.
Yes. I start with the tools, libraries and code your team already uses, and work with your designers and developers to see what’s useful, what’s getting in the way and where the files and the code no longer match. Any development work is scoped together before we start.
Both. A brand identity, website launch, product proof of concept or the first version of a design system usually works well as a defined project. If you need someone to stay involved as the roadmap evolves, or to keep your design system growing with the product, I also take on ongoing engagements. We can start with a focused piece of work if there’s a particular decision or launch you need to get through first.
I’ll give you a fee and timeline once we’ve agreed on what you need me to own. Designing a website with approved copy is a different scope from working through the positioning, writing the copy and building the site. Tidying up an existing component library is likewise a different scope from building a full design system. If you already have a budget, launch date or weekly time commitment in mind, share it early so I can tell you what’s realistic and when I can start.
Process and timelines
A little context on what you’re building, who it’s for and why you’re looking for help now. An existing product, website, deck, component library or short brief is useful. So is a real example: something your sales team explains on every call, a task people keep doing in a spreadsheet, a component your team keeps rebuilding, or a launch your current system can’t support.
For product work, I’ll usually ask someone to walk me through a real task so I can see who’s involved, what decisions they make and where things get difficult. For brand or website work, I’ll want to hear how you describe the business to a prospective customer and what they ask next. For design system work, I’ll look at the files, libraries and code your team uses today, and where design and implementation have drifted apart.
We’ll agree on milestones, who needs to weigh in and when. I share work while there’s still room to change direction. That might mean reviewing a workflow with the people who use it, checking a design system pattern with engineering or asking your sales lead to talk through a draft deck.
| Project | Typical timeline |
|---|---|
| Brand identity | 3–4 weeks |
| Landing page | Around 1 week, including design and development |
| Multi-page website | Around 3 weeks, including design and development |
| Product design | Depends on the scope. I’ll estimate against the workflows and features you need for your next milestone. |
| Design system | Around 3 weeks to 3 months, depending on the scope, product roadmap and what your design and engineering teams need. |
If you’re working towards a fixed launch date, let me know early. I can deliver a focused project in under 1 week, such as a small branding project, a landing page with approved copy and brand assets, or a working proof-of-concept demo built around 1 core workflow.
Experience and industries
I have 7+ years of work experience and have worked on 20+ MVPs and proofs of concept, including 15+ AI products. I’ve also built 10+ design systems, including for Fortune 500 firms, and worked on 20+ websites and 10+ brands. The scale varies from a founder testing an early idea to enterprise design systems supporting 40–50 products each. More about my background
- Healthcare, biopharma and life sciences. Oncology and clinical development tools for scientists, doctors and researchers, hospital EHRs, platforms for clinical staff and patients, and workflows for supply chain, manufacturing and complaints investigations.
- Government and public services. Internal platforms for the people administering healthcare, benefits, childcare and other public programmes.
- Finance, insurance and cybersecurity. Investment research for private equity and venture capital firms, trading education, AI-assisted insurance tools, and product strategy and communication for cybersecurity and digital forensic systems used by military and law enforcement agencies.
- Climate tech, hardware and consumer products. Residential solar, air purification, assistive technology, consumer wearables and travel.
- Brand and website projects have also taken me into robotics, enterprise procurement, food manufacturing, geopolitical advisory and platforms for independent chefs and home bakers.
I start with the people who know the work. On a biopharma complaints project, that meant understanding how someone reports an issue from a manufacturing floor or lab, sometimes on a shared device. Seeing where the report began helped me decide what to ask for at intake and what an investigator could add later. See the complaints platform
At Shweta Labs, which builds cybersecurity and digital forensic systems for military and law enforcement agencies, desk research could only go so far. I spoke with domain experts, mapped investigative workflows and studied competitor tools through hands-on demonstrations to understand where each tool fits in an investigation. See Shweta Labs
On design system work, the people who know the work are the designers and engineers. Much of the thinking behind Flighty’s design system was still held by the founding team, so I started by understanding what mattered most to founding designer Markus Aarstad and his team before we defined the scope together. See Flighty
I’ve taken the same approach on products for defence, clinical development and healthcare operations, and on cybersecurity products in fintech.
Product and design systems
Yes. Much of my enterprise work involved designing one product for 3–4 user groups. I’ve also designed a single shared view for 5–8 roles in larger organisations. Each person needed to follow the same work and quickly see which decisions or tasks were theirs.
In oncology, that meant designing knowledge-mining tools for scientists, doctors and clinical researchers looking for evidence. In residential solar, the work spans a whole service. At SolarSquare, I’m defining a design system for 15+ internal and customer-facing products serving 20+ types of users and stakeholders, from installation through maintenance. In investment research, it meant helping analysts and partners explore a question, compare perspectives and bring their findings into a shared report. See the investment research project
Yes. I start with the decision someone is trying to make. On Atlas, an investment analyst could query internal data and external publications in one place. Getting an answer was only part of the job. The analyst also needed to inspect the sources, discuss the finding with a colleague and decide whether the evidence was strong enough to publish. Those needs shaped the product as much as the AI capability itself. See Atlas
It applies to design systems too. AI tools need context on what to use, when to use it and which rules matter. On the insurance design system, I documented those decisions so different designers and developers could ship screens to production with close to 95% accuracy. See the insurance design system
Yes. On an AI insurance platform, the team was planning tools across 3 domains while the roadmap was still changing. I worked with the design and engineering leads to decide which rules could carry across the suite and where the task needed to shape the interaction. Reading a claim’s history and reassigning a queue of claims called for different behaviour, even when both used a table. See the insurance design system
I also work with teams whose product already has a distinctive design language. For Flighty, I brought the system together across iOS and Apple Watch so a growing team could build with it without losing what makes Flighty feel like Flighty. See Flighty
Brand, websites and decks
I’d listen to how your team explains the business on a sales call. If that explanation lands, but the website leaves people confused, I’d start with the site. If the founders, sales team and product team each give a different answer to “Why would someone choose you?”, it’s worth working on positioning before redesigning pages. From there, we can decide how much of the existing identity still works.
Yes. With Shweta Labs, I interviewed domain experts and mapped investigative workflows to understand how its cybersecurity and digital forensics technology was used. That helped me decide what to explain to the people using it, what a buyer needed to understand and what belonged in an investor conversation.
With Fluid Intelligence, I helped the founder decide how much a prospective client needed to understand about the AI consultancy before a first call and what was better discussed once he knew more about their business. About 1 month after launch, he told me prospects were arriving with more context and he was spending less time explaining the consultancy’s approach. See Fluid Intelligence
Yes. I worked on the websites for Jeyyam Group, a food manufacturer with 45 years of history, and Chanawala, its new venture. Someone discovering Chanawala for the first time had different questions from a partner researching the group behind it. I also built decks the team could use with partners, internal stakeholders and potential financiers.
I look at what brings each person to the site. For Trupeer, someone evaluating the product for an enterprise needed to understand where it would fit in their organisation. Someone about to record their first walkthrough wanted to know how to get started. Both questions shaped what went on the landing pages and what belonged in the resource section. See my work with Trupeer
Yes. I design and build websites, often in Framer, and plan the handover around what your team expects to change. For Peak3, via Bright Studios, I put the emphasis on the website’s design system, so the internal team could publish pages for smaller launches without the site looking incoherent. For Fluid Intelligence, I built reusable templates so the team could add pages as the consultancy grew. We’ll agree on what you want to manage yourselves before I start the build. See the Fluid Intelligence website project
I’ve built investor, sales, partnership and internal stakeholder decks for Seed to Series C startups, companies at the IPO stage and beyond, and Fortune 500 teams.
My background in design and go-to-market helps me shape the story as well as the slides. An investor needs to understand why the business can grow. A buyer often needs a deck they can take back to colleagues who missed the meeting. A prospective partner needs to see what working together would look like. I build the narrative around the decision you want that particular audience to make.
Can I see work closer to what we’re building?
Yes. Tell me who uses your product and what you’re trying to work through. I can point you to a relevant case study or arrange a private walkthrough of work I’m able to share. Sometimes the closest example comes from your industry. Sometimes it’s a team in a different field that had to solve the same problem.
Get in touch