Product Designer & Next.js Developer (Full-Stack)

@jignesh06

Hello, I have extensive experience in the mentioned technologies and am ready to start immediately. Let’s connect via chat to discuss the project requirements further. Thank you, Jignesh

@w3loop

Hi, Your mobile-first, action-focused approach is exactly how I would structure Welcome Finance—moving away from traditional finance pages toward comparison cards, calculators, progressive content and clear application CTAs. I bring 11+ years of web development and 9+ years of UI/UX experience, with strong Figma, responsive frontend, React, SEO and performance experience. I can own the Figma design system and frontend implementation, with the CMS architecture planned around reusable blocks so your SEO team can manage product pages, comparison data, content and metadata independently. I want to be transparent that I would review the existing architecture and your preferred Sanity/Strapi workflow before confirming the final technical scope rather than overstate platform-specific experience. I can start with the mobile UX architecture and homepage/product-page prototype. Thanks, Bhupendra | W3LOOP

@aakaashberi

Two things in your spec pull against each other, worth resolving now. You want Lighthouse mobile 95+ out of the box, and the SEO team injecting scripts through the CMS without calling a developer. Those are in tension: the first GTM container, chat widget and pixel added that way takes you well below 95. The fix is to shape the requirement, not refuse it - a structured JSON-LD field they edit freely, plus a controlled script slot with a documented performance budget. Schema markup is safe; arbitrary third-party tags move the number. Second, the indicative repayment slider. Lending to limited companies and LLPs is generally outside FCA regulated activity, so your framing is right. But an indicative figure shown to a business is still marketing, and if any product could reach a sole trader or small partnership the picture changes. Build implication: the slider's rate and term assumptions live in the CMS and are versioned, so compliance can change them without a deploy and you can show what was displayed on a given date. Third, a limit worth setting with your Head of SEO: a headless CMS lets them build pages from existing block types, not invent layouts. So the phase one block library - comparison table, data badges, disclosure toggle, CTA band, FAQ - decides whether they ever need me again. I have not built a finance marketplace and have no public repo of one. My live reference is edtechvibe.com. 12,500 buys phase one. Aakaash

@obademio1

Hello, I can deliver what you need. I have read the details you shared and I understand the outcome you want. I am an experienced and specialized freelancer with 10+ years of practical experience in PHP, JavaScript, WordPress, Web Development. Visit my profile to check my latest work and reviews from past clients. Looking forward to working with you, connect in chat. Talk soon, Olusoji

@roveme

Welcome Finance requires a complete transformation from a traditional informational website into an interactive, workspace-style marketplace targeting UK Limited Companies and LLPs. This proposal outlines a three-phase approach to deliver a mobile-first, high-performance platform that converts visitors through clean comparison blocks and calculators, seamlessly directing them to your external application form. The ultimate goal is clear: a platform where your Head of SEO operates with 100% independence, launching product pages, spinning up blogs, modifying comparison tables, and injecting schema scripts without developer involvement.

@RinkuAppDevPro

Hi, I can handle both the UI/UX and development, starting with a mobile-first Figma system for the 15+ product pages, homepage, resources and blog, using comparison cards, data badges, calculators and progressive disclosure instead of dense content blocks. With 5+ years of full-stack/UI/UX experience and 65+ projects delivered, I’m comfortable taking ownership from Figma through deployment and documentation. I’d be happy to review your existing branding and application flow and suggest the initial workspace structure. Let's start. thanks