The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Premium Software Company Website built in React + Tailwind CSS.
Live Project: https://52dd0a91.lemoncapswebsite.pages.dev/
Built for a software company with a focus on clean UI, fast loading, and trust-building design.
Stack: React, Tailwind CSS, Framer Motion
Features: Responsive, SEO-friendly, High PageSpeed, Modern Animations
Perfect for: SaaS, Software Agencies, IT Startups
Timeline: 3 days delivery.
DM for live demo and Figma file.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Lekki Vault is a small sneaker shop on Admiralty Way in Lekki, run by one guy, Tobi. He's got a tight rotation of rare and everyday pairs, and the problem was simple: people would walk in wanting to try something on, but half the time their size wasn't even out, or Tobi was mid-conversation with someone else and they just left. So now there's a "book a fitting" option, pick a free 30-min slot, say what pair and size you want, show up, it's pulled and ready. No calls, no "come back later," and Tobi's not guessing who's actually going to show.
Feel free to tweak "half the time their size wasn't even out" if that's not quite the real quirk you had in mind, happy to adjust once you tell me what actually bugged you building it.
I like this visual
A component for Sandbox Platform, showing the boot sequence
Elaro Solar - From solar enquiry to a meaningful next step
Business: Elaro Solar | A small residential rooftop solar installer serving Pune, with a lean field team and a mix of homeowners who range from “I want solar now” to “I’m still comparing my options".
Location: Pune, India
Approach: Front door + follow-through
💯 The problem
For a homeowner, going solar starts with a simple question. For the installer, turning that interest into a real appointment means figuring out whether the home is serviceable, understanding what the homeowner actually needs, finding the right time, assigning the right specialist, and knowing what happens after the visit.
I wanted to remove that operational friction without building another generic booking form or another all-in-one solar CRM.
🧠 The solution
Elaro turns an uncertain solar enquiry into a structured, confirmed appointment, and keeps the work moving afterward.
The homeowner goes through a short, contextual assessment instead of a long form. Questions are introduced only when they change the next decision. Serviceability, home details, ownership, goals, and timing determine whether the customer gets :
- a home assessment
- a phone consultation, or
- a learning path.
The calendar is not just a list of available times. It uses a mechanism that considers technicians' capability, working hours, appointment duration, service area, scheduling buffers, and conflicts before confirming a slot.
On the owner side, the model is deliberately simple:
Customer → Home → Job → Appointment
That lets the team see the customer relationship, the work being done, and the appointment itself as separate but connected things. A completed appointment can create the next action instead of becoming a dead end.
🙌 The part I pushed further
I kept asking: what happens when this customer comes back months later?
Elaro remembers the home and the work associated with it. After phone verification, it can recognise a previously assessed home, reconnect the customer with the appropriate job, and let them move forward without repeating the entire process.
When the system isn't certain that it's the same home, it asks instead of guessing.
Elaro remembers the work that happened, not just the appointment that happened.
That also meant solving the underlying rules for matching homes, preventing duplicate open jobs, safely reopening previous work, and keeping the customer and owner experiences in sync.
🚀 How I approached it
The build started with competitor and workflow research rather than UI. Existing solar products already cover areas such as bill analysis, satellite roof design, proposals, and payments, while established intake flows can become lengthy and information-heavy.
So I deliberately focused on the layer before and around the appointment.
I mapped the journey, defined the system model and interaction rules, designed the visual system, considered accessibility across the experience, and then implemented and tested the product iteratively in Lovable.
🎉 What I built :
A complete customer-to-owner experience spanning:
Intelligent assessment → serviceability → appointment routing → constraint-based scheduling → specialist assignment → Jobs & Appointments → follow-through → returning customer → Home Memory → Solar Journey
See it in action here: https://elarosolar.lovable.app/
🙌 Owner Team sign-in
email: owner@elarosolar.example
password: ElaroDemo2026
lovablechallengeProduct StrategyUX DesignBusiness StrategyProduct DesignWeb DevelopmentFigmaGoogle DocsLovable
Liked the thinking behind problem solving. 💯