# Shreyas Kothakonda: Full Context > Webflow Certified Partner and front-end developer based in Bengaluru, India. 6+ years building high-performance websites for startups, agencies, and enterprise clients. This is the extended context file. For the concise version, see https://www.shreyas.live/llms.txt ## About Shreyas Kothakonda specialises in Figma-to-production web development. Core stack: Webflow, Astro, Next.js, React, TypeScript, GSAP, and Framer. Webflow Certified Partner and a semi-finalist at the Webflow Conf 2023 Speed Build Challenge in San Francisco. Works with clients in India and worldwide on fixed-price or retainer terms, and replies within 24 hours. ## Technologies Webflow, React, Next.js, Astro, TypeScript, JavaScript, HTML, CSS, Tailwind CSS, GSAP, Framer, Shopify, Liquid, n8n, Make, and Zapier. ## Services in detail Every service below has a dedicated page. Its overview, deliverables, process, and FAQs follow. ### Webflow Development Webflow Certified Partner building fast, semantic, CMS-powered websites from Figma to production. Pixel-perfect, 90+ Lighthouse, editor-friendly, for SaaS, agencies, and startups worldwide. Page: https://www.shreyas.live/services/webflow-development Overview: I design and build production Webflow sites from Figma. They're fast, semantic, fully CMS-driven, and easy for your team to edit. No bloat, no broken responsive, no developer needed for every copy change. What's included: - Pixel-perfect from Figma: Every spacing value, font, and breakpoint rebuilt to match your design, using Webflow variables and reusable components, not hardcoded one-offs. - CMS & dynamic content: Collections modelled for blog, case studies, careers, pricing, or whatever your content needs, so non-technical teammates publish without a developer. - Interactions & motion: Scroll effects, page transitions, and micro-interactions built with Webflow Interactions or GSAP where it earns its weight. - Performance built in: Semantic markup, image optimisation, deferred scripts, and structured data deliver 90+ Lighthouse and green Core Web Vitals from day one. - Integrations, no bloat: Finsweet Attributes, Memberstack, Zapier, and custom JS as needed, never a pile of plugins slowing the site down. - Editor-ready handoff: Webflow Editor set up with clear field labels and a Loom walkthrough, so your team owns content updates from day one. Process: 1. Discovery call: A 30-minute call to understand goals, content structure, and any technical constraints, then a fixed-price scope so there are no surprises. 2. Proposal & scope: A fixed-price proposal with timeline, deliverables, and revision rounds defined up front. 3. Design in Figma: Full desktop + mobile mockups for your approval before a single Webflow component is built (or I work from your existing Figma). 4. Webflow build: Component-based build with CMS, interactions, and responsive polish, with a staging link shared as each page lands. 5. QA & launch: Cross-browser and device QA, final SEO and performance checks, domain connection, and 30 days of post-launch support. FAQs: Q: How much does a Webflow website cost? A: It depends on scope: page count, CMS complexity, e-commerce, and memberships all factor in. I quote a fixed price after a discovery call so there are no surprises. Get in touch for a tailored quote. Q: How long does a Webflow build take? A: Most marketing sites take 2–4 weeks from a finished Figma file, depending on page count and feedback speed. I share a timeline before starting and a staging link as each page is built. Q: What is a Webflow Certified Partner? A: Webflow Certified Partners are vetted by Webflow and have demonstrated expertise across design, development, and CMS builds. Certification means I follow Webflow's best practices for performance, accessibility, and editor experience. Q: Can you redesign or fix my existing Webflow site? A: Yes. I handle full redesigns (Figma → Webflow rebuild) and existing-site work like adding pages, fixing responsiveness, migrating to CMS, or improving performance scores. Q: Will my team be able to edit the site without a developer? A: Yes, that's the point. I set up the Webflow Editor with clear field labels and record a Loom walkthrough, so your team updates content confidently without touching the build. Q: Do you work with clients outside India? A: Yes. I work with clients in the US, UK, Australia, and across Europe. Everything is async-friendly with clear documentation, so timezones aren't a blocker. ### Figma to Webflow Pixel-perfect Figma to Webflow conversion by a Webflow Certified Partner. Every spacing, interaction, and breakpoint rebuilt exactly, with clean classes, full CMS, responsive fidelity, and a recorded handoff. Page: https://www.shreyas.live/services/figma-to-webflow Overview: You have the design. I'll build it in Webflow, faithfully reproducing every detail of your Figma file with clean, component-based code your team can maintain. No interpretation, no cleanup tax. What's included: - Faithful Figma conversion: Every spacing, type, and colour decision lands exactly, using Webflow variables and styles, not hardcoded values. - Component architecture: Webflow symbols and classes mirror your Figma component library so future changes propagate globally. - Interaction parity: Hover states, modals, scroll animations, and transitions built to match your prototype. - Responsive fidelity: Mobile and tablet built from your Figma responsive frames, not auto-scaled guesses. - Token pipeline: Figma variables map 1:1 to Webflow variables, so your design system stays the source of truth. - Asset & SEO ready: Assets exported, compressed, and set up with alt text, lazy loading, and clean semantic markup. Process: 1. File review: I audit your Figma for completeness (missing states, inconsistent tokens, unclear responsive) and flag anything before the build. 2. Webflow project setup: Global styles, colour variables, and typography classes configured to mirror your Figma design system. 3. Page build: Pages built section-by-section in priority order, with a staging link shared after each for your review. 4. Interaction build: Hover states, animations, and scroll effects implemented to match the Figma prototype. 5. Handoff: A recorded Loom walkthrough, Editor setup, and documentation of any decisions made during the build. FAQs: Q: What format do you need the Figma file in? A: A shared view or edit link is fine. Ideally pages are organised with clear frame names and a components page. I'll flag anything unclear during the file-review stage. Q: How much does Figma to Webflow conversion cost? A: It depends on the size of the file and how much custom interaction is involved. I quote a fixed price after reviewing your Figma file. Reach out for a tailored quote. Q: Will the Webflow site match my Figma exactly? A: Yes, pixel-accurate rebuilds are the whole point. I match spacing, type, and colour across breakpoints, and flag anything in the design that won't translate cleanly to the web before building it. Q: How long does a Figma to Webflow conversion take? A: A 5–8 page site with standard components takes 5–10 business days. More complex designs or heavy custom interactions take longer, scoped per project. Q: Do you handle Auto Layout and responsive design? A: Yes. Auto Layout maps naturally to Webflow's flex and grid, and I hand-tune tablet and mobile breakpoints from your responsive frames rather than relying on auto-scaling. Q: Who owns the Webflow project after? A: You do. The project is transferred to your Webflow account with a clean, documented build and an Editor set up for your team. ### Framer Development High-craft Framer websites with motion that means something, designed, built, and shipped fast. Custom components, CMS, and SEO by a developer who builds in both Framer and Webflow. Page: https://www.shreyas.live/services/framer-development Overview: I design and build Framer sites for founders and creative teams who want a polished, animated site live quickly. Custom layouts, tasteful motion, CMS-driven content, and SEO set up right, never a recycled template. What's included: - Custom design: Original layouts built to your brand, never a marketplace template everyone else is running. - Motion & interactions: Framer's animation tools used with restraint to add polish without hurting performance. - CMS-driven content: Blog, changelog, and careers collections so non-technical teammates can publish independently. - Custom code components: Reusable React components for Framer that go beyond the default library. - Responsive fidelity: Desktop, tablet, and mobile breakpoints tuned by hand, not just scaled down. - SEO & performance: Meta tags, OG images, sitemap, and fast load times configured from the start. Process: 1. Discovery call: A 30-minute call to understand goals, content, and any technical needs, then a fixed-price quote. 2. Design direction: Layout and visual direction agreed in Framer or Figma before the build, so there are no surprises. 3. Framer build: Pages built as reusable components with the CMS wired up and content structured for easy editing. 4. Motion & QA: Animations layered in, then cross-browser and device QA to catch anything off. 5. Launch & handoff: Domain, SEO, and analytics connected, plus a recorded walkthrough for editing content. FAQs: Q: How much does a Framer website cost? A: It depends on page count, animation, and whether you need custom code components. I quote a fixed price after a quick discovery call. Get in touch for a tailored quote. Q: Should I use Framer or Webflow? A: Framer is faster to ship and excellent for landing pages, launches, and motion-heavy sites. Webflow gives more control over markup, deeper CMS structures, and complex multi-template builds. I build in both and recommend the right fit honestly. Q: How long does a Framer build take? A: Most Framer sites go live in 1–2 weeks from kickoff, depending on scope and how quickly feedback comes back. I share a timeline before starting. Q: Can you build custom components in Framer? A: Yes. Beyond the default library, I build reusable interactive React (code) components for Framer, for interactions and patterns the standard elements can't do. Q: Can you migrate my existing site to Framer? A: Yes. I can rebuild an existing WordPress, Wix, or custom site in Framer, preserving your content while improving the design, motion, and performance. ### Shopify Development Custom Shopify stores that load fast and sell better. Custom themes, conversion-focused product pages, speed optimisation, and headless builds for D2C brands in India and worldwide. Page: https://www.shreyas.live/services/shopify-development Overview: I build and customise Shopify stores for brands that have outgrown templates. A custom theme, conversion-focused product pages, and a fast, headless option when you need it, built to match your brand and sell better. What's included: - Custom theme: A Shopify theme built or heavily customised to your brand, not a marketplace template everyone uses. - Conversion-focused PDPs: Product pages designed to build trust and move shoppers to checkout, with reviews, trust signals, and clear CTAs. - Speed optimisation: Faster load through clean Liquid, optimised images, and trimming the apps that drag the store down. - App & tool integration: Reviews, subscriptions, analytics, and marketing tools integrated cleanly, not bolted on. - Headless option: For maximum speed, a headless build with Next.js and the Shopify Storefront API, with Shopify as the backend. - India + global commerce: Razorpay/PayU, GST, and domestic shipping for Indian D2C, plus Shopify Payments for global brands. Process: 1. Discovery call: Understand your products, brand, and goals, then scope a fixed-price build. 2. Design direction: Agree on the storefront and product-page direction before building. 3. Theme build: Theme and templates built in Liquid (or headless), wired to your catalog. 4. Apps & QA: Integrations added, checkout tested, and the store optimised for speed. 5. Launch & handoff: Store goes live with analytics connected and a guide for managing products. FAQs: Q: How much does a custom Shopify store cost? A: It depends on the number of templates, integrations, and whether you need a headless build. I quote a fixed price after understanding your catalog and goals. Reach out for a tailored quote. Q: Custom theme or a Shopify template? A: Templates are fine to start, but they limit branding and often load slowly with added apps. A custom or heavily-customised theme gives you a faster, on-brand store that converts better. I'll tell you honestly which makes sense for your stage. Q: Do you build headless Shopify stores? A: Yes. For brands that need maximum speed and a fully custom front end, I build headless stores with Next.js and the Shopify Storefront API, keeping Shopify as the commerce backend. Q: How long does a Shopify build take? A: A customised theme build usually takes 2–4 weeks depending on the number of templates and integrations. I share a timeline before starting. Q: Can you migrate my store from WooCommerce or Wix? A: Yes. I handle product, collection, and blog migrations from WooCommerce, Wix, Webflow Commerce, and BigCommerce, and advise on customer/order history migration during scoping. Q: Do you work with Indian D2C brands? A: Yes. I've built for D2C brands across India, handling Razorpay and PayU alongside Shopify Payments, GST tax configuration, and domestic shipping providers. ### Next.js Development Design-engineered Next.js front ends that are fast, accessible, and built to last. Custom web apps, headless-CMS marketing sites, and React builds by a developer who designs and engineers. Page: https://www.shreyas.live/services/nextjs-development Overview: When a project needs more than a website builder can offer, I build it in Next.js and React: custom web apps, marketing sites with real logic, and headless front ends. Six years of front-end work and a designer's eye, in one person. What's included: - React & Next.js builds: Modern App Router front ends with server components, TypeScript, and clean, maintainable code. - Headless CMS integration: Wired to Prismic, Sanity, Contentful, or Shopify so your content team stays fully independent. - Core Web Vitals: Built for fast LCP, low CLS and INP, and 90+ Lighthouse out of the box, not as an afterthought. - Accessibility: Semantic markup, keyboard support, and ARIA where it's needed, built in and never bolted on. - Motion with GSAP: Smooth, performant animation when the design calls for it, without sacrificing speed. - Deploy & DX: Shipped to Vercel or Netlify with CI, previews, and documentation so your team can build on it. Process: 1. Scoping call: Understand the product, data, and design, then agree on architecture and a clear quote or rate. 2. Foundations: Project setup, design tokens, and component structure established first so the rest inherits them. 3. Build: Pages and features built as reusable, typed components against your CMS or API. 4. Performance & QA: Optimised for Core Web Vitals and tested across browsers, devices, and assistive tech. 5. Deploy & handoff: Shipped to Vercel or Netlify with CI and documentation so your team can build on it. FAQs: Q: How much does a Next.js website cost? A: It varies widely with scope: a marketing site with a headless CMS is very different from a custom web app. I quote a fixed price or a clear rate after a scoping call. Get in touch for a tailored quote. Q: When should I choose Next.js over Webflow or Framer? A: Pick Next.js when you need custom logic, app-like interactivity, deep integrations, or full control over performance and markup. For standard marketing sites, Webflow or Framer are faster and cheaper, and I'll say so rather than over-engineering your project. Q: Which CMS do you use with Next.js? A: I work with Prismic, Sanity, Contentful, and others. I recommend one based on your team's editing needs and budget, then integrate it so content updates never require a developer. Q: Do you handle accessibility and performance? A: Yes. Both are built in, not bolted on. I ship semantic, keyboard-accessible markup targeting WCAG AA, and tune for Core Web Vitals (fast LCP, low CLS/INP) from the start. Q: How long does a Next.js build take? A: A marketing site with a CMS usually takes 3–6 weeks. Web apps depend on feature scope. I share a milestone timeline before starting. Q: Can you work with our existing engineering team? A: Yes. I write typed, documented, componentised code and follow your conventions, so I can plug into an existing team or hand off cleanly to one. ### AEO & AI Search Optimization Become the source AI assistants cite. Answer Engine Optimization for ChatGPT, Perplexity, and Google AI Overviews: structured data, answer-first content, llms.txt, and the agent-discovery layer most sites are missing. Page: https://www.shreyas.live/services/aeo-ai-optimization Overview: As people ask ChatGPT and Perplexity instead of clicking blue links, being the source those answers cite is the new front page of search. I make your site machine-readable, citation-worthy, and impossible for answer engines to skip. What's included: - Structured data & schema: Service, FAQPage, Person, and Organization schema so AI systems can parse exactly what you offer and who you are. - llms.txt & crawler access: An llms.txt file and crawler config that let AI agents discover and summarise your key pages and services. - Answer-first content: Content restructured around the questions your buyers ask, with direct answers AI can quote verbatim. - Entity & internal linking: Clear entity relationships and internal links so AI understands how your pages and services connect. - Technical SEO & speed: Core Web Vitals, clean semantic HTML, sitemaps, and metadata: the foundations AI and search both reward. - Agent-discovery layer: Link headers, an API catalog, and content signals: the machine-facing layer most sites haven't built yet. Process: 1. AI-visibility audit: I check how ChatGPT, Perplexity, and Google AI currently describe you and your competitors, and find the gaps. 2. Schema & structured data: Add Service, FAQ, Person, and Organization schema across your key pages so machines understand them. 3. Answer-first content: Restructure pages around buyer questions with concise, quotable answers and FAQ sections. 4. llms.txt & crawler setup: Publish an llms.txt, confirm AI crawlers are allowed, and wire up sitemaps, Link headers, and metadata. 5. Measure & iterate: Track AI citations, branded mentions, and referral traffic from AI tools over time, and refine. FAQs: Q: What is AEO (Answer Engine Optimization)? A: AEO is optimising your website so AI answer engines (ChatGPT, Perplexity, Google AI Overviews, and others) can read, understand, and cite it. Instead of only ranking in a list of links, the goal is to be the trusted source the AI quotes directly in its answer. Q: How is AEO different from SEO? A: SEO optimises to rank in search result lists; AEO optimises to be cited inside AI-generated answers. They overlap (both need clean technical foundations and good content) but AEO leans harder on structured data, answer-first writing, FAQ markup, entity clarity, and machine-readable files like llms.txt. Q: Will this get my site cited by ChatGPT and Perplexity? A: There are no guarantees with AI systems, but sites that get cited consistently share clear structured data, direct answer-first content, strong topical authority, and fast, crawlable pages. AEO puts those signals in place to maximise the chance your site is the source quoted. Q: How do you measure AI search visibility? A: I baseline how AI assistants describe you and your competitors before starting, then track changes in citations, branded mentions, and referral traffic from AI tools over time, alongside traditional search rankings. Q: Does schema markup still matter in 2026? A: More than ever. Structured data is how machines reliably extract what your page means: Service, FAQPage, and Person/Organization schema make your content unambiguous to answer engines, which makes it far easier to cite. Q: Do I need this if I already do SEO? A: AEO builds on good SEO rather than replacing it. If you have solid technical SEO, AEO adds the machine-facing layer (schema depth, answer-first structure, llms.txt, and entity clarity) that turns rankings into citations. ### Webflow to Astro Migration Migrate your Webflow site to Astro for near-instant load times, full code ownership, and no monthly fees. Zero-JS-by-default rebuild with your design and SEO preserved, by a Webflow Certified Partner. Page: https://www.shreyas.live/services/webflow-to-astro-migration Overview: Astro ships zero JavaScript by default, one of the fastest ways to build a content site. I migrate Webflow sites to Astro so you keep the design, gain near-instant load times, own your code, and drop the monthly subscription. What's included: - Pixel-faithful rebuild: Your Webflow design rebuilt in Astro exactly: same layout, type, and spacing across every breakpoint. - Near-perfect performance: Zero JS by default means most pages hit 95–100 Lighthouse and load almost instantly. - Content & CMS migration: Webflow CMS moved into Astro content collections or a headless CMS (Prismic, Sanity, Storyblok) so your team keeps editing. - SEO preserved: Meta, structured data, sitemaps, and 301 redirects carried over so rankings and traffic hold. - Own your code & hosting: No more monthly Webflow fees or lock-in: deploy to Vercel, Netlify, or Cloudflare and own everything. - Islands for interactivity: Where you need it, interactive components hydrate as isolated islands, without shipping JS to the whole page. Process: 1. Audit & inventory: I map every page, CMS collection, interaction, and SEO asset on your Webflow site, then quote a fixed price. 2. Architecture & content: Astro project set up with your design tokens and a content-collection or headless-CMS structure. 3. Rebuild in Astro: Pages rebuilt as reusable Astro components matching your Webflow design at every breakpoint. 4. Content migration & QA: Content moved over, then cross-browser and device QA plus a full SEO and redirect check. 5. Launch with redirects: Go live with 301 redirects, sitemap, and analytics in place so nothing drops in search. FAQs: Q: Why migrate from Webflow to Astro? A: Teams move to Astro for three reasons: speed (zero JavaScript by default), cost (no recurring Webflow subscription), and ownership (you control the code and host anywhere). The trade-off is that editing needs a developer or a connected headless CMS rather than the Webflow Designer. Q: Will my SEO and Google rankings be preserved? A: Yes. I carry over all meta tags, structured data, and headings, and set up 301 redirects for every URL. Done right, a Webflow-to-Astro migration preserves rankings and usually improves them thanks to faster load times. Q: How much does a Webflow to Astro migration cost? A: It depends on page count, CMS complexity, and interactions. I quote a fixed price after auditing your current site. Get in touch for a tailored quote. Q: Can my team still edit content after migrating? A: Yes. I connect a headless CMS (Prismic, Sanity, Storyblok) or use Astro content collections so your team keeps publishing without touching code. We pick the option that fits your workflow during the audit. Q: Should I choose Astro or Next.js? A: Astro wins for content and marketing sites where speed and simplicity matter and you ship little interactivity. Next.js is the right call when you need a full web app: auth, dashboards, complex state. I build both and recommend honestly. ### Webflow to Next.js Migration Migrate your Webflow site to Next.js without losing your design or your rankings. SEO-safe migration with 301 redirects and preserved schema, by a Webflow Certified Partner who builds in Next.js daily. Page: https://www.shreyas.live/services/webflow-to-nextjs-migration Overview: You've outgrown Webflow: you need auth, dashboards, real integrations, or full control. I rebuild your site in Next.js with the design intact and every URL, redirect, and schema preserved, so rankings hold. What's included: - Faithful rebuild: Your Webflow design rebuilt in Next.js with the App Router, matching layout and interactions at every breakpoint. - Headless CMS: Content migrated to Prismic, Sanity, or Contentful so non-technical teammates keep publishing independently. - Custom functionality: Auth, dashboards, search, payments, and API integrations that Webflow simply can't do natively. - Core Web Vitals: Server components, image optimisation, and caching tuned for fast LCP and strong Lighthouse scores. - SEO-safe migration: Meta, structured data, sitemap, and 301 redirects carried over so rankings and traffic hold. - Full ownership: Your code, your hosting (Vercel/Netlify), your content layer, with no platform lock-in or seat fees. Process: 1. Audit & inventory: I map every page, CMS collection, integration, and SEO asset on your Webflow site, then quote a fixed price. 2. Architecture & headless CMS: Next.js project and the right headless CMS (Prismic/Sanity/Contentful) set up around your content model. 3. Rebuild in Next.js: Pages and features rebuilt as typed, reusable components against the CMS and any APIs, with the design preserved. 4. Content migration & QA: Content moved across, then performance, cross-browser, and a full SEO + redirect audit. 5. Launch with redirects: Ship to Vercel or Netlify with 301 redirects, sitemap, and analytics in place so nothing drops in search. FAQs: Q: Will my SEO and rankings survive the migration? A: Yes. I preserve all meta tags, structured data, and headings, and implement 301 redirects for every URL so search engines carry rankings to the new pages. Next.js server rendering keeps content fully crawlable, and the speed gains usually help. Q: When should I migrate from Webflow to Next.js? A: When you need things Webflow can't do natively: user authentication, dashboards, complex data, custom integrations, or app-like interactivity. If you only need a marketing site, staying on Webflow (or moving to Astro) is usually cheaper and faster. Q: How much does a Webflow to Next.js migration cost? A: It depends on page count, CMS complexity, and any app features (auth, dashboards, integrations). I quote after auditing your site and requirements. Reach out for a tailored quote. Q: Which CMS will my content move to? A: I work with Prismic, Sanity, and Contentful and recommend one based on your team's editing needs and budget, then migrate your Webflow CMS content into it so publishing stays self-serve. Q: Can you keep my exact design? A: Yes. The design is preserved pixel-for-pixel. The point of migrating is to keep what works visually while gaining the engineering. I rebuild faithfully, not redesign (unless you want a refresh). Q: How long does it take? A: A marketing-site migration usually takes 3–6 weeks depending on page count and CMS complexity. App features extend the timeline; I share a milestone plan before starting. ### Webflow Cloud Custom apps and dynamic functionality on Webflow Cloud. Deploy Astro and Next.js apps on Webflow's infrastructure, right alongside your marketing site. Webflow Certified Partner. Page: https://www.shreyas.live/services/webflow-cloud Overview: Webflow Cloud lets you ship real applications (Astro or Next.js, server logic, APIs, and dynamic data) hosted on Webflow's own infrastructure, right next to your marketing site. I design and build them end to end. What's included: - Astro & Next.js apps: Full framework apps that are server-rendered, fast, and deployed straight to Webflow Cloud's edge network. - Server logic & APIs: Routes, server functions, and third-party API calls for functionality the Designer can't do natively. - Dynamic data: Databases and external data sources wired in, so the app reflects live state, not static content. - DevLink components: Webflow-designed components pulled into code with DevLink, keeping the design system in sync. - Git push-to-deploy: Connected to your repo with preview builds and one-click deploys, a real engineering workflow. - One domain, one brand: The app mounts on a path of your main site, so users never leave your domain or your design language. Process: 1. Scope & architecture: We define what the app does, the data it needs, and how it mounts onto your existing Webflow site. 2. Project setup: Astro or Next.js project wired to Webflow Cloud, your repo, and DevLink for shared components. 3. Build: Pages, server logic, and data integrations built as typed, reusable components with preview deploys. 4. QA & performance: Tested across browsers and devices, tuned for fast loads and Core Web Vitals on the edge. 5. Deploy & handoff: Shipped to Webflow Cloud with push-to-deploy and documentation so your team can build on it. FAQs: Q: What is Webflow Cloud? A: Webflow Cloud is Webflow's platform for hosting full framework applications, Astro or Next.js, on Webflow's own infrastructure. It lets you run custom apps, server logic, and dynamic data under the same domain as your Webflow marketing site. Q: When should I use Webflow Cloud instead of native Webflow? A: Use it when you need functionality the Designer can't do natively, like dashboards, tools, authenticated areas, dynamic data, or custom server logic, but want it to live alongside your Webflow site rather than on a separate host. Q: Which frameworks does Webflow Cloud support? A: Astro and Next.js. I pick based on the app: Astro for fast, mostly-content apps, and Next.js when you need richer interactivity, auth, or complex state. Q: Can it share my Webflow site's design? A: Yes. With DevLink I pull your Webflow-designed components into the app's code, so the app stays visually consistent with the rest of your site and updates as the design system evolves. Q: Do you handle deployment? A: Yes. I set up push-to-deploy from your Git repo with preview builds, ship to Webflow Cloud's edge, and document the workflow so your team can deploy confidently. ### GSAP, Motion & Interactions Scroll-triggered effects, page transitions, and micro-interactions built to the pixel with GSAP and Motion, for Webflow, Framer, and Next.js. Animation that improves comprehension, never decoration. Page: https://www.shreyas.live/services/gsap-animations Overview: I build the kind of motion that makes a site feel considered: scroll storytelling, page transitions, and micro-interactions, hand-built with GSAP and Motion. Performant, accessible, and reduced-motion safe. What's included: - Scroll-triggered effects: ScrollTrigger reveals, pins, and scrubbed timelines tuned to your content's pacing. - Page & state transitions: Smooth, branded transitions between pages and UI states that feel native. - Micro-interactions: Buttons, hovers, and inputs with tactile feedback that makes the UI feel alive. - SVG & canvas animation: Path-draw diagrams, animated logos, and lightweight canvas effects. - Performance budget: Animations built for 60fps with GPU-friendly transforms, never janky scroll. - Accessibility built in: Every effect respects prefers-reduced-motion and never traps or distracts. Process: 1. Motion audit: We review your site and goals, then identify where motion will actually help, and where it won't. 2. Direction: I prototype the key interactions so we agree on feel, timing, and intensity before full build. 3. Build: Animations built with GSAP/Motion as reusable, guarded modules that drop cleanly into your stack. 4. Performance & a11y: Profiled for 60fps and wired with reduced-motion fallbacks across browsers and devices. 5. Handoff: Documented, parameterised code so your team can reuse and tweak the motion later. FAQs: Q: What is GSAP? A: GSAP (GreenSock Animation Platform) is the industry-standard JavaScript animation library. It gives frame-precise control over timelines, scroll-triggered effects, and SVG, far beyond what website-builder interactions can do natively. Q: Can you add GSAP animation to my Webflow or Framer site? A: Yes. I add custom GSAP and Motion code to Webflow, Framer, and Next.js sites (scroll effects, transitions, and micro-interactions) without breaking the editor or the existing build. Q: Will animations slow my site down? A: Not when built right. I animate GPU-friendly properties, lazy-load where needed, and keep a performance budget so motion stays at 60fps and never hurts Core Web Vitals. Q: Do you handle accessibility and reduced motion? A: Always. Every effect respects the prefers-reduced-motion setting and degrades to a static, fully-usable experience. Motion is an enhancement, never a barrier. Q: Can motion actually improve conversions? A: When it guides attention, clarifies relationships, and gives feedback, yes, it improves comprehension and trust. I build motion with that intent and avoid decoration that just adds load. ### Webflow Audits A thorough Webflow audit covering performance, SEO, CMS structure, accessibility, and maintainability, with a clear, prioritised list of what to fix and why. From a Webflow Certified Partner. Page: https://www.shreyas.live/services/webflow-audit Overview: Inherited a messy Webflow project or unsure why your site is slow? I review your build end to end, covering performance, SEO, CMS structure, accessibility, and maintainability, and hand you a prioritised, plain-English fix list. What's included: - Performance review: Core Web Vitals, image optimisation, render-blocking scripts, and load-time wins specific to Webflow. - SEO audit: Meta tags, heading structure, schema, sitemap, redirects, and crawlability issues that cost rankings. - CMS structure: How your collections, references, and content model hold up as the site grows, and where they'll break. - Accessibility check: Semantic markup, colour contrast, keyboard navigation, and ARIA gaps measured against WCAG. - Maintainability: Class naming, component reuse, and Editor experience: how easy the site is to run day to day. - Prioritised fix list: Every finding ranked by impact vs effort, with a Loom walkthrough so you know exactly what to tackle first. Process: 1. Access & context: You share read access and a few goals; I learn what the site needs to do and who maintains it. 2. Deep review: I work through performance, SEO, CMS, accessibility, and maintainability against a structured checklist. 3. Score & prioritise: Each area is scored and every issue ranked by impact and effort, so the path is obvious. 4. Report & walkthrough: You get a written report plus a recorded Loom walking through findings and recommendations. 5. Optional fixes: Want it handled? I can implement the fixes myself, or your team can run the list independently. FAQs: Q: What does a Webflow audit include? A: A structured review of five areas (performance, SEO, CMS structure, accessibility, and maintainability), scored individually, with every issue ranked by impact and effort. You get a written report and a recorded Loom walkthrough. Q: Do I need to give you full access? A: Read access is enough for the audit itself. If you'd like me to implement fixes afterwards, we'll set up the appropriate access then. Q: How long does an audit take? A: Most audits are delivered within a few business days of getting access, depending on the size and complexity of the site. Q: Will you fix the issues too? A: I can. The audit stands on its own, but many clients have me implement the prioritised fixes, or hand the list to their own team to action. Q: Can you audit a Webflow site built by someone else? A: Yes, that's one of the most common reasons people request an audit. I review inherited Webflow builds and give you an honest read on quality, risks, and what to fix. ### Webflow Training 1:1 and team Webflow training, from fundamentals through advanced interactions, CMS, and clean class systems. Practical, hands-on sessions from a Webflow Certified Partner. Page: https://www.shreyas.live/services/webflow-training Overview: Practical, hands-on Webflow training for designers, marketers, and teams, from fundamentals to advanced interactions, CMS, and a clean class system. Live sessions built around your real project, not generic slides. What's included: - Tailored to your level: Beginner to advanced: I assess where you are and pitch every session accordingly. - Built on your project: We work in your real Webflow project, so training translates directly to your site. - 1:1 or team workshops: Focused one-on-one coaching or structured team workshops to standardise how you build. - Recorded sessions: Every session is recorded so you can revisit it, and the team can onboard later. - Clean conventions: Learn a maintainable class system and component approach, not just where the buttons are. - Follow-up support: A window of async Q&A after sessions so questions on real work don't go unanswered. Process: 1. Goals & level check: A short intake to understand your experience, your project, and what you want to walk away able to do. 2. Tailored plan: I shape a session plan around your goals: fundamentals, CMS, interactions, or a mix. 3. Live sessions: Hands-on, screen-shared sessions working in your real project, recorded for later. 4. Practice & review: You apply it between sessions; we review your work and tighten the rough edges. 5. Handoff & support: Notes, recordings, and a window of async Q&A so the learning sticks. FAQs: Q: Who is Webflow training for? A: Designers moving into Webflow, marketers who want to update sites without a developer, and teams that want to standardise on a clean, scalable build. I tailor every session to your level and your project. Q: Is training 1:1 or for teams? A: Both. I run focused one-on-one coaching and structured team workshops. Team sessions are great for getting everyone on the same conventions and workflow. Q: Do we use my real project? A: Yes. Wherever possible we work in your actual Webflow project so the training applies directly to the site you're building or maintaining. Q: Are sessions recorded? A: Yes. Every session is recorded so you can revisit it and onboard teammates later, and I share notes alongside. Q: How is this different from free tutorials? A: Tutorials are generic; training is built around your level, your project, and your questions, including the clean class systems and conventions that tutorials rarely teach well. ### Custom Framer Components Reusable, interactive React code components for Framer that go beyond the default library: custom interactions, data-driven UI, and effects the standard elements can't do. Page: https://www.shreyas.live/services/framer-components Overview: When Framer's built-in elements hit their ceiling, I build custom React code components that are reusable, configurable, and on-brand. Interactions, data-driven UI, and effects the default library simply can't do. What's included: - Property controls: Every component exposes editable controls in Framer, so designers tweak it without code. - Reusable & on-brand: Built to your design tokens and reusable across pages and projects, not one-offs. - Data-driven UI: Components that fetch from an API or CMS to render live, dynamic content inside Framer. - Accessible by default: Keyboard support, focus states, and ARIA built in, because interactive doesn't mean inaccessible. - Performance-minded: Lightweight, lazy where it helps, and animated on GPU-friendly properties for smooth scroll. - Documented handoff: Clear docs on each control so your team can reuse and configure components confidently. Process: 1. Define the component: We agree what it does, the controls designers need, and how it should behave and animate. 2. Build in React: I build a typed React code component with Framer property controls and your design tokens. 3. Wire data & motion: Any API/CMS data and interactions are added, then tuned for performance and accessibility. 4. Test in Framer: Dropped into your project and tested across breakpoints, devices, and edge cases. 5. Handoff: Documented controls and usage notes so your team can reuse it anywhere. FAQs: Q: What is a Framer code component? A: A custom React component you drop into Framer like any other element, with editable property controls. It lets you add interactions, logic, and live data that Framer's default library can't do, while designers still configure it visually. Q: Can designers still edit it without code? A: Yes. I expose property controls for the things you'll want to change (text, colours, speed, data source) so designers tweak the component in Framer without touching React. Q: Can a component pull in live data? A: Yes. Code components can fetch from an API or CMS and render dynamic content (counters, feeds, charts, or anything data-driven) inside your Framer site. Q: Will it stay on-brand and accessible? A: I build to your design tokens and bake in keyboard support, focus states, and ARIA, so components feel native to your site and remain accessible. Q: Can you build one component, or a whole set? A: Either. I build one-off components or a reusable library your team can use across pages and projects, with documentation for each. ### Shopify Theme Dev Custom Shopify themes built from scratch or tailored from Dawn: fast, on-brand, and conversion-focused, with custom sections merchants can edit. Liquid, JavaScript, and the theme editor done right. Page: https://www.shreyas.live/services/shopify-theme-development Overview: Custom Shopify themes, built from scratch or tailored from Dawn, that load fast, match your brand exactly, and give your team editable sections in the theme editor. Liquid done cleanly, no bloat from stacked apps. What's included: - Custom or Dawn-based: Built from scratch or tailored from Dawn, whichever gives you the best result for the budget. - Editable sections: OS 2.0 sections and blocks so your team builds and edits pages in the theme editor, no developer needed. - Conversion-focused PDPs: Product pages designed and built to convert: variants, trust signals, and clear calls to action. - Speed optimisation: Lean Liquid, lazy-loaded media, and minimal app bloat for fast load and better Core Web Vitals. - App integrations: Reviews, subscriptions, search, and marketing apps integrated cleanly without wrecking performance. - Editor handoff: Documentation and a Loom walkthrough so your team runs and updates the store confidently. Process: 1. Discovery: We map your products, brand, and the sections and templates the store actually needs. 2. Design direction: Design in Figma or adapt your existing designs, agreed before any Liquid is written. 3. Theme build: Custom or Dawn-based theme built with editable OS 2.0 sections and clean, documented Liquid. 4. Speed & QA: Optimised for performance and tested across browsers, devices, and key purchase flows. 5. Launch & handoff: Published, with a recorded walkthrough so your team can edit and extend the theme. FAQs: Q: Should I use a custom theme or a Shopify template? A: Templates are fine to start, but they limit branding and often slow down as you add apps. A custom or heavily-customised theme gives you a faster, on-brand store with exactly the sections you need. I'll advise honestly based on your stage and budget. Q: Do you build from scratch or customise Dawn? A: Both. Tailoring Dawn (Shopify's reference theme) is cost-effective and fast; a from-scratch build gives total control. I recommend the right path for your goals and budget. Q: Can my team edit the store after launch? A: Yes. I build OS 2.0 sections and blocks so your team adds and edits pages in the theme editor without a developer, and I hand off a recorded walkthrough. Q: Will the theme be fast? A: Yes. Performance is a priority. I write lean Liquid, lazy-load media, and avoid unnecessary app bloat, tuning for fast loads and good Core Web Vitals. Q: Can you integrate apps like reviews or subscriptions? A: Yes. I integrate reviews, subscriptions, search, and marketing apps cleanly, keeping the storefront fast and the code maintainable. ### Figma to Shopify Pixel-perfect Figma-to-Shopify conversion. Your design built into a fast, conversion-ready Shopify store with editable sections and clean Liquid. No template compromises. Page: https://www.shreyas.live/services/figma-to-shopify Overview: You've designed the store in Figma, and I build it into Shopify exactly as drawn. A fast, conversion-ready storefront with merchant-editable sections and clean Liquid, not a template forced to fit your brand. What's included: - Pixel-perfect conversion: Spacing, type, colour, and layout matched to your Figma across every breakpoint. - Conversion-ready PDPs: Product pages built from your design to sell: variants, trust, and clear calls to action. - Editable sections: OS 2.0 sections so your team edits and reorders content in the theme editor, no developer needed. - Responsive by hand: Tablet and mobile tuned from your responsive frames, not just scaled down. - Clean, fast Liquid: Lean, documented Liquid and lazy-loaded media for fast loads and good Core Web Vitals. - App integrations: Reviews, subscriptions, and search wired in cleanly without bloating the storefront. Process: 1. File review: I review your Figma file, flag anything that won't translate cleanly to Shopify, and confirm scope. 2. Theme setup: A custom or Dawn-based theme set up to your design tokens: type, colour, and spacing system. 3. Build: Templates and sections built pixel-faithfully with editable OS 2.0 blocks and clean Liquid. 4. Speed & QA: Optimised for performance and tested across browsers, devices, and the full purchase flow. 5. Launch & handoff: Published, with a recorded walkthrough so your team can edit and grow the store. FAQs: Q: Will the Shopify store match my Figma exactly? A: Yes. Faithful conversion is the whole point. I match spacing, type, colour, and layout across breakpoints, and flag anything in the design that won't translate cleanly to Shopify before building it. Q: What do you need from me to start? A: A shared Figma link with desktop and mobile frames, ideally organised with clear naming. I'll review it and flag anything unclear during the file-review stage. Q: Can my team edit the store after? A: Yes. I build OS 2.0 sections and blocks so your team edits and reorders content in the theme editor without a developer, and I hand off a recorded walkthrough. Q: Custom theme or based on Dawn? A: Either one. I recommend the right approach for your design and budget. Tailoring Dawn is fast and cost-effective; a from-scratch build gives total control. Q: Will the store be fast? A: Yes. I write lean Liquid, lazy-load media, and avoid app bloat, tuning for fast loads and good Core Web Vitals so the design also performs. ### Performance Optimization Core Web Vitals and Lighthouse optimization for Webflow and Next.js: image, font, and render-blocking fixes that speed up load, lift SEO, and improve conversions. Measured, not guessed. Page: https://www.shreyas.live/services/performance-optimization Overview: Slow sites lose rankings and sales. I audit and fix performance at the source (images, fonts, scripts, and render-blocking assets) to push Core Web Vitals into the green and Lighthouse into the 90s. Measured before and after. What's included: - Image optimisation: Right formats, sizes, lazy-loading, and a sensible CDN strategy, usually the biggest single win. - Font loading: Subsetting, preloading, and font-display tuned to kill render-blocking and layout shift. - Render-blocking fixes: Deferred and split JavaScript and CSS so the page paints fast and stays interactive. - Layout stability: Reserved space and stable embeds to drive CLS toward zero, so no more jumping content. - Third-party scripts: Audited, deferred, or removed: analytics, chat, and pixels are common silent killers. - Measured results: Lab and field data captured before and after, so the improvement is proven, not promised. Process: 1. Measure: I baseline your Core Web Vitals with lab and field data to find what's actually slow, not guesses. 2. Diagnose: Each bottleneck is traced to a cause: images, fonts, scripts, third parties, or render path. 3. Fix at the source: Optimisations implemented in the code or Webflow project, with no band-aid plugins. 4. Re-measure: Vitals and Lighthouse re-run to confirm the gains and catch any regressions. 5. Report: A clear before/after report so you can see exactly what changed and the impact. FAQs: Q: What are Core Web Vitals? A: Core Web Vitals are Google's user-experience metrics: LCP (how fast the main content loads), CLS (how stable the layout is), and INP (how responsive it is to input). They're a ranking factor and a strong proxy for real-world speed. Q: Will faster pages actually help SEO and sales? A: Yes. Page speed is a confirmed ranking factor, and faster pages measurably reduce bounce and lift conversions. Performance work is one of the highest-ROI technical investments you can make. Q: Do you optimise Webflow and Next.js? A: Both, plus Astro and Shopify. The principles are the same (images, fonts, scripts, render path) but I adapt the fixes to each platform's tooling and constraints. Q: Do you use a plugin or fix the real cause? A: I fix the real cause. Plugins often mask problems or add their own overhead. I optimise images, fonts, scripts, and the render path at the source so the gains are durable. Q: How do I know it worked? A: I capture lab and field data before and after and share a clear report. You see the Core Web Vitals and Lighthouse scores move, so the result is measured, not claimed. ### Technical SEO Technical SEO done by a developer: schema markup, structured data, sitemaps, meta, crawlability, and Core Web Vitals so the right pages get found, indexed, and shown as rich results. Page: https://www.shreyas.live/services/technical-seo Overview: The SEO that lives in the code: schema markup, clean structure, sitemaps, crawlability, and fast pages. I fix the technical foundations so search engines can find, understand, and reward your content, and show it as rich results. What's included: - Structured data & schema: Article, Product, FAQ, Breadcrumb, and Organization schema so pages qualify for rich results. - Crawlability & indexing: Robots, canonicals, redirects, and internal linking so the right pages get crawled and indexed. - Sitemaps & meta: Clean XML sitemaps, titles, descriptions, and Open Graph generated correctly across large sites. - Core Web Vitals: LCP, CLS, and INP fixes: speed is a ranking factor, and I tune it at the source. - Site architecture: Heading hierarchy, URL structure, and information architecture that search engines understand. - Monitoring & fixes: Search Console issues triaged and fixed, with a clear report of what changed and why. Process: 1. Technical audit: I crawl your site and review schema, indexation, structure, and Core Web Vitals against a full checklist. 2. Prioritised plan: Findings ranked by impact and effort so we fix the things that move rankings first. 3. Implementation: Schema, sitemaps, redirects, meta, and performance fixes implemented directly in the code. 4. Validation: Rich-result and structured-data testing, plus Search Console checks to confirm everything's clean. 5. Report & monitor: A clear report of what changed, with monitoring so new issues are caught early. FAQs: Q: What is technical SEO? A: Technical SEO is the work that helps search engines crawl, understand, and index your site: structured data, sitemaps, canonicals, crawlability, site architecture, and Core Web Vitals. It's the foundation content and links build on. Q: How is technical SEO different from AEO? A: Technical SEO optimises to rank in traditional search results; AEO optimises to be cited inside AI answer engines. They share foundations like schema and clean structure. I offer both, and they reinforce each other. Q: Does schema markup still matter? A: More than ever. Structured data is how machines reliably extract what a page means: Article, Product, FAQ, and Organization schema make content unambiguous and qualify it for rich results in search. Q: Do you fix Core Web Vitals? A: Yes. Core Web Vitals are a ranking factor and a UX win. I fix LCP, CLS, and INP at the source (images, render-blocking assets, and layout shifts), not with a plugin band-aid. Q: Will this work on Webflow, Shopify, or Next.js? A: Yes. I implement technical SEO across Webflow, Shopify, Astro, and Next.js, adapting to each platform's strengths and constraints while keeping the fundamentals consistent. ### Any Platform → Webflow Migration Migrate from WordPress, Squarespace, Wix, or Framer to Webflow, with content, structure, and SEO fully preserved, 301 redirects, and a faster, easier-to-edit site. Webflow Certified Partner. Page: https://www.shreyas.live/services/platform-to-webflow-migration Overview: Moving to Webflow from WordPress, Squarespace, Wix, or Framer? I migrate your content, structure, and SEO faithfully, with 301 redirects so rankings carry over, and leave you a faster site your team can actually edit. What's included: - Content migration: Pages, posts, and media moved into a clean Webflow CMS structure, not a copy-paste mess. - SEO preservation: Meta, headings, schema, and image alt carried over so search engines see continuity, not a reset. - 301 redirect mapping: Every old URL mapped to its new home so rankings and backlinks transfer cleanly. - Faithful redesign: Rebuilt to match or improve your current design, responsive and on-brand across breakpoints. - CMS modelling: Collections and references structured for how you publish, so content stays self-serve in Webflow. - Launch & handoff: DNS cutover handled carefully, with a recorded walkthrough so your team runs the new site. Process: 1. Audit & inventory: I map every page, URL, CMS collection, and SEO asset on your current site before anything moves. 2. Structure & design: We agree the Webflow CMS structure and whether to rebuild faithfully or refresh the design. 3. Build & migrate: The site is rebuilt in Webflow and content migrated into clean collections, page by page. 4. Redirects & SEO: 301 redirects mapped for every URL, with meta and schema carried over and validated. 5. Launch & monitor: Careful DNS cutover, then I monitor Search Console for any issues and fix them fast. FAQs: Q: Will I lose my SEO or rankings migrating to Webflow? A: Not when it's done right. I preserve meta, headings, structured data, and content, and map a 301 redirect for every URL so search engines carry rankings to the new pages. Done carefully, migrations protect rankings, and the speed gains often help. Q: Which platforms do you migrate from? A: WordPress, Squarespace, Wix, Framer, Drupal, and custom or hand-coded sites. The process adapts to each source, but the goal is the same: faithful content, preserved SEO, and a cleaner Webflow build. Q: Will my content come across? A: Yes. Pages, posts, and media are migrated into a clean Webflow CMS structure modelled around how you publish, not a one-off copy-paste that's painful to maintain. Q: Can you keep my current design? A: Yes. I can rebuild faithfully to match your existing design, or use the migration as a chance to refresh it. Either way it's responsive and on-brand across breakpoints. Q: How long does a migration take? A: It depends on page count and CMS complexity. I share a milestone timeline after auditing your current site, and handle the launch carefully to avoid downtime. ### AI Automations Workflow automation and AI agents with n8n, Zapier, Make, and custom code to connect your tools, automate the busywork, and put AI to work on real tasks. Practical automation, not hype. Page: https://www.shreyas.live/services/ai-automations Overview: I connect your tools and automate the repetitive work (lead routing, content ops, data sync, reporting) with n8n, Zapier, Make, and custom code, adding AI where it genuinely helps. Practical automation that saves real hours. What's included: - Workflow automation: Multi-step automations across your stack with n8n, Zapier, or Make, built to be reliable, not brittle. - AI agents & LLM steps: Classification, drafting, summarising, and routing with LLMs, added only where they genuinely help. - Custom integrations: API and webhook integrations for tools that don't have a native connector, including custom code. - Data sync: Keep CRMs, sheets, databases, and apps in sync automatically, with conflict handling that holds up. - Error handling & alerts: Retries, fallbacks, and notifications so a failed run never silently loses data. - Docs & ownership: Clear documentation and handoff so your team can run, monitor, and extend the automations. Process: 1. Map the process: We walk through the manual task step by step to find what's automatable and where AI fits. 2. Design the workflow: I design the automation (triggers, steps, data, and failure paths) and agree it with you. 3. Build & integrate: Built in n8n, Zapier, Make, or code, wired to your tools and APIs with proper error handling. 4. Test & harden: Run against real cases, add retries and alerts, and confirm it behaves under edge cases. 5. Handoff & monitor: Documented and handed off, with monitoring so issues surface early, not in your inbox at 2am. FAQs: Q: What can you automate? A: Repetitive, rule-based work across your tools: lead capture and routing, onboarding, content publishing, data sync between apps, reporting, and AI-assisted triage. If a person does it the same way every time, it's usually a candidate. Q: Which tools do you use? A: n8n, Zapier, and Make for workflow automation, plus custom code and APIs when a native connector doesn't exist. For AI steps I use LLMs and agents where they add real value. Q: Do I need AI, or just automation? A: Often plain automation solves the problem and AI isn't needed. I add AI only where it genuinely helps (classifying, drafting, or summarising) rather than bolting it on for the sake of it. Q: Is it reliable? A: Reliability is the point. I build in retries, fallbacks, and alerts so a failed run never silently loses data, and I document everything so your team can monitor it. Q: Will my team be able to manage it? A: Yes. I hand off clear documentation and a walkthrough, and where it makes sense build in tools you control, so you're not dependent on me to keep it running. ## Typical engagements Shreyas commonly works with: - Startups launching new products - Agencies needing white-label Webflow development - Companies migrating from WordPress or Webflow - SaaS teams building marketing websites - Businesses improving Core Web Vitals and technical SEO - Ecommerce brands building Shopify storefronts - Teams that need an independent senior developer rather than a full agency - Clients working across IST, GMT, or EST timezones - Projects that mix marketing platforms (Webflow, Framer) with custom apps (Next.js on Vercel) and automation (n8n, Make, custom APIs) ## Selected work Client projects across healthcare, fintech, SaaS, creative agencies, and ecommerce, all Figma-first and shipped on time. See https://www.shreyas.live/work ## Contact - Email: hello@shreyas.live - Book a call: https://www.shreyas.live/contact - Hire (for recruiters): https://www.shreyas.live/hire - LinkedIn: https://www.linkedin.com/in/shreyas-kothakonda/ - Webflow: https://webflow.com/@shreyaskothakonda - GitHub: https://github.com/shreyaskothakonda