Frequently Asked Questions

Before work begins, Desisle needs clarity on six things: your goals and what a successful outcome looks like; the success metrics you will use to measure it (conversion rate, task completion, activation, NPS, etc.); your target audience — who uses the product and what they need; the key flows or use cases the product must support; any existing assets such as brand files, a live codebase, or a partial design system; and any hard constraints around budget, timeline, or technology stack. Most importantly, there needs to be one designated decision-maker on your side. A single owner eliminates review bottlenecks, keeps communication clean, and ensures the engagement moves at the pace it should.

Yes — many of the best projects begin with a rough idea rather than a detailed brief. Desisle runs a structured shaping process that clarifies goals, identifies the riskiest assumptions, defines a realistic scope, and builds a lightweight prototype to validate the core concept before larger investment is made. You do not need to arrive with a specification document. Thinking out loud is completely fine. The shaping phase is designed precisely for that.

Yes. Desisle signs NDAs as a standard part of any engagement. You can use your own NDA template or Desisle's. Both are reviewed before signing. This covers all proprietary information, product concepts, user data, and business strategy shared during the engagement.

Yes. Desisle runs a structured UX audit that covers heuristic evaluation, analytics review, key user journey mapping, and a competitive benchmark. The output is a scorecard and a prioritized roadmap. This audit typically takes 2–3 weeks and serves as an honest foundation — so any proposed work is grounded in evidence rather than assumption. Audits can be standalone engagements or the entry point into a larger redesign.

Desisle is remote-first. Day-to-day collaboration happens through Slack, Figma, ClickUp or Jira, and Loom video updates. On-site visits are available for high-value moments like kick-off workshops, alignment sessions with multiple stakeholders, or design sprint intensives — usually one focused day achieves more than weeks of back-and-forth.

Desisle offers three productized monthly plans that cover most engagement types, plus custom quotes for scopes that fall outside them. Pricing is outcome-based — you are paying for progress and results, not hours logged. The factors that most significantly shift the price are: scope complexity, the speed of delivery required, how deep the user research needs to go, the number of third-party integrations, and the size of the embedded team. Discounts are available for multi-month or multi-product engagements.

Fixed project is the right choice when scope is clearly defined and finite — building a specific MVP, redesigning a particular product area, or delivering a standalone design system. Fixed projects follow milestone-based payments (50/30/20) with defined end states. Retainer is better when your needs are ongoing and evolving — continuous feature development, regular UX improvements, sustained growth work, or embedded team extension. Retainers offer monthly flexibility, weekly sprint cycles, and the ability to reprioritize as your product and market change. A one-month pilot is available to evaluate fit.

No. Desisle does not bill by the hour. Hourly billing misaligns incentives — it rewards time spent rather than value created. Instead, engagements are scoped based on outcomes: what needs to be achieved, by when, and at what level of depth. This keeps the focus on results and makes budgeting predictable for clients.

Yes. A one-month pilot is available on retainer plans. This lets you experience the working style, communication cadence, and output quality before committing to a longer engagement. Most clients who run a pilot continue — but the pilot exists to make the decision easy and low-risk.

Yes. One-month pilot on retainers.

Multi-month or multi-product engagements.

Invoices can be raised in USD, EUR, or INR depending on your location and preference. Payment terms are: retainers prepaid monthly, fixed projects on a 50/30/20 milestone structure. Late payments trigger a grace period after which active work pauses.

Every engagement follows a five-phase process: Discover → Strategize → Design → Develop → Grow. Discover: Research, stakeholder interviews, competitive analysis, and problem framing. Strategize: Define success metrics, user journeys, feature scope, and roadmap. Design: Wireframes, UI design, prototype, and iterative feedback loops. Develop: Engineering, QA, integrations, and launch. Grow: Post-launch analytics, optimization, and continuous improvement. Not every phase applies to every engagement — a pure design brief skips the Develop phase, for example. The process is calibrated to what you need.

Collaboration runs on weekly sprints with a structured check-in to review what was done, what's next, and any blockers. Between sprint calls, async updates happen via Slack and ClickUp or Jira so you always know what's in progress without needing a meeting. A dedicated point of contact — a lead designer or PM — owns all communication on the Desisle side. No email threads, no confusion about who to ask.

Yes — respectfully, and always with data. A design partner who only nods along is not adding value. If user research, analytics, or design principles suggest a different approach, Desisle will say so clearly and explain why. The goal is the best outcome for your users and your business, not agreement for its own sake.

Structured comments in Figma + sprint reviews.

Yes. Weekly summaries + monthly impact reports.

All change requests go through a clear process: document → estimate → approve → proceed. The new request is logged, a time and cost estimate is provided, explicit approval is obtained, and only then does work begin. This protects both sides — it keeps the project on track and ensures nothing is delivered without mutual agreement on its scope and cost.

Yes. You receive weekly summaries of what was completed, what is in progress, and what is planned for the next sprint. On retainer engagements, a monthly impact report ties design and development work back to the KPIs you care about. These reports are designed to be useful in internal stakeholder updates.

Standard deliverables include: Figma source files with organized frames and components; interactive prototypes; design tokens (color, spacing, typography); a design system or component library; all necessary asset exports in required formats; and developer specs. Design decisions are documented in Notion or PDF format. All files and IP transfer to you upon final payment.

Yes. Notion or PDF decision logs.

Handoff happens through Figma Inspect with annotated component specs, spacing and type documentation, interaction notes, and any relevant API or integration guidance. For larger systems, Storybook documentation can be set up on request. Desisle also conducts design QA on built interfaces to ensure implementation fidelity before launch.

Yes. Design QA and functional checks.

You do — after final payment is received. This includes all source files, design systems, code, and documented decisions. Unused concept explorations created during the engagement can be reused by Desisle unless the contract explicitly restricts this. Everything produced specifically for your project is yours.

Yes. With maintenance plans.

All project assets are stored in secure cloud environments with restricted access — typically Figma (for design), Notion (for documentation), and your chosen Git repository (for code). Access is limited to team members actively working on your project. Desisle does not store client assets on personal devices or unsecured platforms.

PII is only accessed when strictly necessary for the work — for example, when conducting user interviews or analytics work that requires real data. When it is accessed, least-privilege principles apply: only the team members who need it can access it, and only for the duration required. For sensitive regulated data (healthcare, fintech), Desisle designs with compliance constraints built in. Legal sign-offs remain your responsibility.

Yes, when appropriate and compliant.

You own project outputs; unused explorations can be reused unless restricted in contract.

MVP Design: 3–6 weeks (design only; build time depends on scope) Product Redesign: 4–8 weeks depending on product complexity and stakeholder alignment Design System: 4–5 weeks for build or refactor UX Audit & Strategy: 2–3 weeks These are design-phase timelines. Development runs parallel or sequentially depending on the project structure. Expedited timelines are possible if capacity allows — a rush fee applies.

If capacity allows. Rush fee applies.

Usually within 3–5 business days after the agreement is signed and the first payment is received. The kick-off session is typically scheduled within that window, and active design work begins in the same week. If you have an urgent timeline, flag it early — start dates can sometimes be accelerated.

Yes. Desisle is based in Bangalore (IST) and maintains overlap windows with GMT and EST for synchronous calls and reviews. Async communication via Slack and Loom covers the gaps. Most international clients find the time zone difference negligible once async workflows are established — often it actually accelerates turnaround because work progresses overnight.

Design & Prototyping: Figma and FigJam for all interface design, component libraries, and collaborative workshops. Research & Testing: Maze or Lookback for moderated and unmoderated usability testing when required. Documentation: Notion for decision logs, briefs, and knowledge bases. Whiteboarding: Miro for workshops and journey mapping.

Desisle builds in: React and Next.js for frontend web applications; Node.js for backend APIs and server logic; PHP and Laravel for enterprise or CMS-backed applications; WordPress for content-managed sites; Webflow for no-code marketing sites; MySQL for relational databases; REST and GraphQL for API design; and React Native or Flutter for cross-platform mobile apps.

GA4, GSC, GTM, Ahrefs/SEMrush, Meta/Google/LinkedIn Ads.

ClickUp/Jira, Slack, Loom.

Desisle works across SaaS, AI products, IT and ITSM platforms, cybersecurity, manufacturing, healthcare, fintech, and e-learning, among others. The studio takes a research-led approach to every domain — deep industry expertise is built through immersion, not assumed from the start. For regulated spaces like healthcare and fintech, designs are produced with compliance constraints built in; legal sign-offs remain the client's responsibility.

We learn fast. Research-led approach.

We design with compliance constraints in mind. You handle legal sign-offs.

An MVP design engagement covers the full design arc: discovery and problem framing; user flow mapping; low-fidelity wireframes to establish structure and logic; high-fidelity UI design; an interactive prototype for testing and stakeholder alignment; and complete developer specs for handoff. Add-ons include user testing, pitch deck design, and investor narrative support.

Yes, if you have access. We can also help recruit.

The goal of an MVP is to prove the core value proposition with the least possible surface area. Desisle helps identify which features are essential to that proof and which are phase two. A common mistake is designing too much too early — an MVP that tries to do everything delays learning and increases risk. The design is also built with a clear growth path, so scaling into v1 and beyond is straightforward, not a rebuild.

Yes. We design with a growth path.

Yes. As an add-on.

3–6 weeks for design; build depends on scope.

A redesign is typically the right call when: key metrics (activation, retention, conversion) have stalled and incremental patches haven't moved them; accumulated UX debt has made the product slow and expensive to change; the visual design no longer reflects the brand's current positioning; or a new user segment has been identified that the existing design doesn't serve well. If you are spending more time working around the current design than on it, it's time for a redesign.

Large changes are de-risked through a combination of A/B testing where possible, staged rollouts that release changes to a subset of users first, and clear changelogs communicated to existing users. Baseline KPIs are established before launch so the post-launch comparison is clean. Stakeholder alignment workshops are run when internal disagreement could otherwise block progress or reverse decisions after launch.

We run alignment workshops with evidence.

Yes. We modernize without alienating users.

Baseline KPIs → post-launch comparison.

Both — but always starting with an audit. If you have an existing system that is partially working, a refactor is usually faster and less disruptive than a rebuild. If there is no system or what exists is so fragmented it cannot be salvaged, a ground-up build is the right call. The audit determines which path makes sense before any work begins. Deliverables include design tokens (color, typography, spacing, radius, shadow), a component library, pattern documentation, usage guidelines, and governance definitions — covering who owns the system, how it is versioned, and how updates are managed. Team onboarding sessions are included.

Tokens, components, patterns, guidelines, and usage notes.

Yes. Desisle syncs design system components with React, Tailwind, or your existing stack. Tokens are structured to map cleanly to CSS variables or Tailwind config. Storybook documentation is available on request, providing a living reference for developers that stays in sync with the design system as it evolves.

We define roles, versioning, and update cadence.

Yes. Team onboarding sessions.

A Desisle UX audit covers: heuristic evaluation against established usability principles; analytics review to identify drop-off points and friction in real usage data (analytics access is helpful but not mandatory); user journey mapping across key flows; competitive benchmark against 3–5 relevant products; and a prioritized roadmap of improvements ranked by impact and effort. Output: scorecards, a priority action plan, and clear next steps. Can be executed independently or as the foundation for a redesign engagement.

Helpful, but not mandatory.

Strategy workshops run as either two half-day remote sessions or one full on-site day. Sessions are structured to surface alignment gaps, define user needs, prioritize feature bets, and produce a concrete direction for the next phase of the product. The output is actionable: a decision log, a priority plan, and next steps — not just a slide deck with observations.

Scorecards, priority plan, and next steps.

We can execute the roadmap or guide your team.

A design pod is an embedded team extension: 2–4 designers and a strategist who integrate directly into your sprint rituals, use your Slack and project management tools, and work as a seamless part of your product team. Requests are unlimited within sprint capacity and prioritized weekly. There is no queue to join or ticket system to navigate — the pod simply works alongside you. The minimum term is one month, but most partners stay significantly longer. Pods scale as needed and can include developers and growth specialists in addition to designers.

Unlimited within sprint capacity. We prioritize weekly.

1 month. Most partners stay longer.

We use your Slack/Jira/ClickUp and follow your sprint rituals.

IST with overlap windows for your team.

Yes. B2B and B2C require meaningfully different design approaches — B2B tends to prioritize efficiency, information density, and role-based access; B2C prioritizes onboarding clarity, emotional engagement, and conversion. Desisle designs for both, adapting the approach based on the product type, user research, and business model.

Yes. UX writing + full page copy as needed.

Yes. Desisle follows WCAG 2.1 Level AA guidance by default. This covers color contrast ratios, keyboard navigation, focus state visibility, semantic HTML structure, and screen reader compatibility. Accessibility is treated as a design requirement from the first iteration — not a checklist applied after the fact. This is both the right practice and increasingly a legal requirement in many markets.

Microinteractions yes. Motion guidelines on request.

Yes. UX writing — button labels, empty states, error messages, tooltips, onboarding flows — is included as part of the design work because words and layout are inseparable. Full page copy for marketing-facing surfaces is also available when needed.

A full brand identity engagement covers: brand strategy (positioning, values, voice); logo and mark design; a complete visual identity system (color palette, typography, iconography, photography style); brand guidelines documenting usage rules; and templates for recurring touchpoints. File formats delivered: AI, SVG, PNG, PDF, and a Figma system. Collaterals — pitch decks, social templates, stationery, ads — are available as add-ons. Naming and tagline development is also available.

A refresh modernizes an existing identity without breaking recognition — adjusting typography, refining the palette, or evolving the mark. A rebrand signals a more fundamental shift in positioning or audience. Desisle assesses this based on how far the current brand is from where the business needs to be and the risk of alienating existing users. The recommendation is always evidence-based, not stylistically motivated.

AI, SVG, PNG, PDF, and Figma system.

Pitch decks, socials, stationery, ads—on request.

Available as an add-on

A product strategy engagement produces: a clear positioning statement; a feature map aligned to user needs and business goals; documented user flows; a low-fidelity prototype to communicate the vision tangibly; and a product plan with phased priorities. During the engagement, Desisle joins roadmap calls and co-owns the backlog. Team coaching through clinics and training sessions is also available. For teams preparing for investor conversations, Desisle helps craft product narrative and supporting visuals.

Yes. We co-own the backlog during the engagement.

Yes. Clinics and training sessions.

We help craft product narrative and visuals.

Desisle builds: marketing and product websites; web applications and SaaS dashboards; RESTful and GraphQL APIs; WordPress and Webflow sites; and mobile apps via React Native or Flutter. Integrations cover payment gateways, authentication providers, analytics platforms, CRMs, and third-party APIs. Hosting is on AWS, Azure, or Hostinger — or your preferred provider — with SSL and CI/CD pipelines configured as needed.

React/Next.js, Node.js, PHP/Laravel, WordPress, Webflow, React Native/Flutter.

AWS/Azure/Hostinger—or your choice. SSL and CI/CD if needed.

Payment, auth, analytics, CRM, and third-party APIs.

QA covers functional testing (does it work as intended?), responsive testing across screen sizes and devices, performance testing benchmarked against Core Web Vitals targets, and basic security checks. Automated test suites are available as an optional addition. Post-launch support is available via retainer, with defined SLAs for bug triage and fixes.

Yes. Retainers available.

A retainer covers ongoing design needs: new feature design, UX polish on existing flows, landing page design, periodic UX audits, and design system maintenance. Work is prioritized weekly based on highest impact. Desisle does not sell hours — if a sprint has unused capacity, priorities roll forward rather than expiring. Monthly flexibility means plans can be paused or switched as your needs evolve. Weekly progress summaries and monthly outcome reports are standard.

Weekly planning. Highest impact first.

We don’t sell hours. We carry priorities forward.

Monthly flexibility.

Weekly progress + monthly outcomes.

Desisle runs campaigns across SEO, Google Ads, Meta Ads, LinkedIn Ads, YouTube, and email marketing. Content production is included: web copy, blog posts, landing pages, and ad creative. Tracking is set up via GA4, Google Search Console, GTM, and platform pixels. Weekly and monthly performance reports are standard. Landing page design, copy, and development are all in scope. Existing campaigns can be audited and optimized rather than rebuilt from scratch.

Yes. Web copy, blogs, landing pages, and ad copy.

We advise a test budget per market. You control spend.

GA4, GSC, GTM, and platform pixels. Weekly and monthly reports.

Yes. Design, copy, and dev.

SEO is treated as a combination of technical quality and content strategy. On the technical side: clean information architecture, semantic HTML, fast page load times, schema markup, and well-structured internal links. Core Web Vitals targets are LCP under 2.5 seconds, CLS under 0.1, and INP under 200 milliseconds. On the content side: keyword research, search-intent alignment, and content that genuinely answers what users are looking for — including the kind of detailed, question-based content that surfaces in AI-powered search results and LLM responses.

Desisle can act as your embedded design and product arm via retainer or scoped pods — working under your brand (white-label) or as a visible expert depending on your preference. For agencies, this means clean files, documented decisions, and timelines you can present directly to your clients. Co-pitching is available — as a silent partner contributing production capacity or as a named expert who strengthens the pitch. Revenue sharing and joint ventures are considered case by case.

Yes. Under your brand.

Open to both, case by case.

Clean files, comments, and timelines you can present to clients

Yes. As your silent partner or visible expert.

Yes. Desisle offers industry-aligned UI/UX curriculum, live project briefs, workshops, portfolio reviews, and internship pathways for academic institutions. Formats range from 1–2 day workshops to 4–8 week bootcamps to full semester tracks. Students work on real problems with mentor reviews and demo days. Co-branded completion certificates are issued. For top performers, Desisle provides mock interviews, feedback, and referrals.

1–2 day workshops, 4–8 week bootcamps, or semester tracks.

Yes. Co-branded completion certificates.

Yes. With mentor reviews and demo days.

Mock interviews, feedback, and referrals for top performers.

Yes.

Taste, systems thinking, writing, and ownership.

Great case studies. Clear thinking. Real impact.

Yes. Stipend + mentorship. Real projects.

Desisle values taste (the ability to judge what is good and why), systems thinking (seeing how parts connect and affect each other), clear writing (because design is communication), and ownership (driving things to completion without being managed). Strong case studies that show real impact matter more than seniority or credentials. All roles are remote-friendly. To apply: send your portfolio and a short write-up on a product you would improve and why to hello@desisle.com. Internships come with a stipend, mentorship, and real project work — not busywork.

Fixed projects include 30 days of post-launch support covering bug fixes and design adjustments. For ongoing support beyond that window, monthly retainers are available with defined SLAs for bug triage and resolution. Design systems receive quarterly audits and updates under maintenance plans. Bug fixes go through a triage, fix, and tracking process — nothing falls through the cracks.

Yes. Quarterly audits and updates.

We triage, fix, and track. Dev SLAs available.

WCAG 2.1 AA guidance by default.

Clean IA, semantic HTML, fast pages, schema, and internal links.

Desisle targets: LCP (Largest Contentful Paint) under 2.5 seconds; CLS (Cumulative Layout Shift) under 0.1; and INP (Interaction to Next Paint) under 200 milliseconds. These are stack-dependent — the targets are set at project start based on the technology and hosting environment. Performance is tested across device types and connection speeds, not just desktop ideal conditions.

Yes. Desisle sets up GA4, Google Search Console, Google Tag Manager, and platform pixels as standard. Conversion tracking — goal completions, funnel steps, event tracking — is configured and verified. A properly instrumented analytics setup is a prerequisite for the kind of evidence-based design iteration Desisle practices.

Monthly in advance.

Work pauses after grace period.

Refunds are not issued once work has begun. This is de-risked on the front end through clear scope definitions, weekly reviews, and structured feedback processes — so you always know what is being worked on and can course-correct before an entire phase is complete. The milestone structure on fixed projects also means you only pay for work that has been delivered and approved.

Retainers are prepaid monthly. Fixed projects follow a 50/30/20 structure: 50% upfront to begin, 30% at a mid-project milestone, 20% on final delivery. Invoices are raised monthly for retainers and at each milestone for projects. Late payments trigger a grace period after which active work pauses until the account is current. Vendor onboarding paperwork and MSAs are supported.

The process is straightforward: share your goals → Desisle scopes the engagement → you select a plan or agree on a custom quote → kickoff within 3–5 business days. Reach out at hello@desisle.com. Response time is within one business day. Desisle is based in Bangalore and works with clients globally.

Within one business day.

Bangalore. Working globally.