<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Lavendar Solution on Medium]]></title>
        <description><![CDATA[Stories by Lavendar Solution on Medium]]></description>
        <link>https://medium.com/@lavendarsolution?source=rss-04bf72694b60------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qLSIo-55hWgs-EwYoautAg.jpeg</url>
            <title>Stories by Lavendar Solution on Medium</title>
            <link>https://medium.com/@lavendarsolution?source=rss-04bf72694b60------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 02:11:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lavendarsolution/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[We Built a Custom CRM for a Solar Company in 3 Months — Integrated Everything, and Saved Them…]]></title>
            <link>https://medium.com/@lavendarsolution/we-built-a-custom-crm-for-a-solar-company-in-3-months-integrated-everything-and-saved-them-36c9ac470aed?source=rss-04bf72694b60------2</link>
            <guid isPermaLink="false">https://medium.com/p/36c9ac470aed</guid>
            <category><![CDATA[solar-energy]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Lavendar Solution]]></dc:creator>
            <pubDate>Thu, 12 Mar 2026 11:07:30 GMT</pubDate>
            <atom:updated>2026-03-12T11:07:30.044Z</atom:updated>
            <content:encoded><![CDATA[<h3>We Built a Custom CRM for a Solar Company in 3 Months — Integrated Everything, and Saved Them $4,000 a Month</h3><p><em>A real case study on what happens when you stop patching tools together and build one platform that actually works.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_eLxWxnbkrmNGK5B" /><figcaption>Photo by <a href="https://unsplash.com/@publicpowerorg?utm_source=medium&amp;utm_medium=referral">American Public Power Association</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>They came to me frustrated.</p><p>Not because their business was failing — it wasn’t. They were a growing solar panel installation company with a solid pipeline, a reliable crew, and happy customers. The problem was everything <em>behind</em> the work.</p><p>Every morning, their office team was jumping between 7 different platforms just to get through a single job: a lead comes in through <strong>HubSpot</strong>, gets handed off to <strong>Service Fusion</strong> for scheduling, the design goes into <strong>OpenSolar</strong>, the custom data gets tracked in <strong>AppSheet</strong>, field photos get uploaded to <strong>CompanyCam</strong>, <strong>DocuSign </strong>chases down the signature — and then Stripe processes the payment, with zero connection to any of the above.</p><p>Seven tools. Seven logins. Seven monthly invoices. And zero of them talking to each other.</p><p>“We’re spending more time managing our software than managing our jobs,” the operations manager told me on our first call.</p><p><em>That’s exactly the problem — and it’s fixable.</em></p><h3>What They Were Paying For</h3><p>Before we built anything, I did a full audit of their stack:</p><p>But the spreadsheet only tells half the story. Every tool handoff meant manual re-entry. When a lead converted in HubSpot, someone re-typed the job into Service Fusion. When an installer uploaded photos to CompanyCam, someone manually linked them to the right job. When Stripe processed a payment, no one in the field knew about it until someone checked two other tools.</p><p>The subscriptions cost $4,000/month. The broken workflow cost them just as much again in wasted labor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lh0_8tqCP-Gq4QsLW_FqYw.png" /></figure><h3>The Decision: Replace Everything — or Build Around What Works?</h3><p>This is where most developers get it wrong. The instinct is to rebuild everything from scratch and ditch every existing tool. But that’s not always the right call.</p><p>After the audit, we made a deliberate decision: <strong>keep the tools that were genuinely best-in-class, and build a custom CRM that integrates with them directly.</strong></p><p>OpenSolar is an excellent solar design tool — there’s no reason to reinvent it. Stripe is the gold standard for payment processing — we’re not touching it. DocuSign handles legally binding e-signatures with compliance built in — that stays too.</p><p>What we replaced was everything else. And what we built was the <strong>central nervous system</strong> that connects it all.</p><h3>How We Built It — With Claude AI as a Development Partner</h3><p>Three years ago, a project like this would have taken 6–9 months and $60,000–$80,000 minimum. Today, with Claude as an active AI development partner throughout the entire build, we delivered a production-ready, fully integrated platform in <strong>just under 3 months</strong>.</p><p>To be clear: Claude didn’t build the platform. I did. But AI compressed every phase — architecture decisions, schema design, API integration logic, code review, edge case analysis, and client documentation. What used to take a week often took a day.</p><p>The result: faster delivery, lower cost, no quality compromise.</p><h3>What We Built</h3><p>The platform runs on <strong>Laravel</strong> (backend) and <strong>React.js</strong> (frontend), with a dedicated <strong>Mobile App</strong> for the field crew. Here’s exactly what changed — and what stayed:</p><h4><strong>✅ Kept &amp; Integrated: OpenSolar</strong></h4><p>OpenSolar remains the solar design tool. But now, the moment a proposal is finalized in OpenSolar, it <strong>automatically syncs into the CRM</strong> — system specs, panel layout, pricing, and all. No copy-paste. No re-entry. The job record in the CRM is instantly populated and ready for the next step.</p><h4>✅ Kept &amp; Integrated: Stripe</h4><p>Stripe still handles all payment processing — we’re not replacing the best payment infrastructure in the business. But now Stripe is <strong>fully wired into the CRM</strong>. When a deposit is collected or a final payment clears, the job status in the CRM updates automatically. The office team, the project manager, and the field crew all see it instantly. No more “did they pay yet?” emails.</p><h4>✅ Kept &amp; Integrated: DocuSign</h4><p>DocuSign handles the legally binding signatures — compliance intact. But here’s what changed: <strong>every signed document is now automatically uploaded and filed inside the CRM</strong>, attached directly to the correct job record the moment the signature is completed. No one has to log into DocuSign, download the PDF, and manually attach it somewhere else. It just appears — timestamped, organized, and permanently linked to the client file.</p><h3>🔄 Replaced: HubSpot, Service Fusion, AppSheet, CompanyCam, Zapier</h3><p><strong>Custom CRM (replaces HubSpot + Service Fusion + AppSheet)</strong> Full lead pipeline, job scheduling, dispatch board, technician assignments, and real-time reporting — all in one place. When a lead converts, a job is created automatically. When a job is assigned, the crew gets notified. Every status change is tracked without anyone touching a spreadsheet.</p><p><strong>Built-in Photo Documentation (replaces CompanyCam)</strong> Field crews upload job site photos directly from the Mobile App. Every photo is auto-tagged to the correct job, client, and install stage. Accessible instantly from the office dashboard.</p><p><strong>Zapier — gone.</strong> No more automation spaghetti. Everything talks to everything natively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W8HkJR7NYhUklLJDQv3WOw.png" /></figure><h3>Mobile App — The Field Crew’s New Command Center</h3><p>One of the most impactful deliverables of this project was the <strong>dedicated Mobile App</strong> for the installation crew.</p><p>Before, field technicians had no reliable way to see their schedule, update job status, or document their work without calling the office. Now they open the app and see everything assigned to them: job address, system specs, site photos from previous visits, signed contracts, and customer contact details — all pulled live from the CRM.</p><p>They can update job status on-site, upload photos in real time, and mark installs as complete — all from their phone. The office sees it the moment it happens.</p><h3>Unified Notifications: WhatsApp, SMS, Email &amp; In-App</h3><p>One of the most underrated features we built was the <strong>unified notification system</strong> — covering four channels simultaneously:</p><ul><li><strong>WhatsApp</strong> — automated job updates and reminders sent directly to the customer’s WhatsApp</li><li><strong>SMS</strong> — backup alerts for customers who don’t use WhatsApp, and internal crew notifications</li><li><strong>Email</strong> — detailed confirmations, proposal delivery, invoice receipts</li><li><strong>In-App Notifications</strong> — real-time alerts inside the platform for the office team and managers</li></ul><p>Every key event in the job lifecycle — lead assigned, proposal sent, contract signed, install scheduled, payment received — triggers the right notification to the right person on the right channel. Automatically.</p><p>No more customers calling to ask “when is my install?” No more office staff manually sending follow-up emails. The system handles it.</p><h3>What Happened After Launch</h3><p><strong>$4,000/month eliminated.</strong> HubSpot, Service Fusion, AppSheet, CompanyCam, and Zapier — gone. OpenSolar, Stripe, and DocuSign stayed, now fully integrated. The platform paid for itself within the first year.</p><p><strong>Admin time cut in half.</strong> Manual re-entry eliminated. Documents file themselves. Payments update the job automatically. The office manager gets two hours of her day back.</p><p><strong>The field crew actually knows what’s happening.</strong> With the Mobile App, technicians have everything they need before they arrive on site. Zero calls to the office to ask for job details.</p><p><strong>Customers stop chasing updates.</strong> WhatsApp and SMS notifications keep clients informed at every milestone without any manual effort from the team.</p><p><strong>One source of truth.</strong> One record per job. Always current. Accessible by everyone who needs it.</p><h3>What This Means for You</h3><p>The goal wasn’t to replace every tool they had. The goal was to build a platform that makes every tool — and every person — more effective.</p><p>OpenSolar still does solar design. Stripe still processes payments. DocuSign still handles compliance. But now they’re all part of one connected system, instead of seven disconnected ones.</p><p>AI-assisted development made this financially viable for a growing SMB. A 3-month build. A one-time investment. No more $4,000/month in subscriptions. No more duct tape between platforms.</p><h3>Find Out What Your Stack Is Costing You</h3><p>I offer a free 30-minute platform audit for solar companies, logistics businesses, and field service operations who want an honest look at whether a custom platform makes financial sense.</p><p>No pitch. Just numbers.</p><p>👉 <a href="https://lavendarsolution.com/"><strong>lavendarsolution.com</strong></a></p><p><strong><em>Kevin </em></strong><em>is the founder of Lavender Solution and a Full Stack Engineer with 8 years of experience building custom platforms for solar companies, SaaS startups, medical providers, and e-commerce operations across 10+ countries. Lavender Solution specializes in replacing multi-tool SaaS stacks with unified, AI-enhanced custom platforms that eliminate recurring software costs. Top Rated on Upwork and Workana.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36c9ac470aed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Claude Code Max Plan vs Cursor Ultra Plan —  Why Claude’s Max Plan Wins by a Mile]]></title>
            <link>https://medium.com/@lavendarsolution/claude-code-max-plan-vs-cursor-ultra-plan-why-claudes-max-plan-wins-by-a-mile-a79d911cbc8c?source=rss-04bf72694b60------2</link>
            <guid isPermaLink="false">https://medium.com/p/a79d911cbc8c</guid>
            <category><![CDATA[comparison]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[ai-coding]]></category>
            <category><![CDATA[cursor]]></category>
            <category><![CDATA[claude-code]]></category>
            <dc:creator><![CDATA[Lavendar Solution]]></dc:creator>
            <pubDate>Sun, 12 Oct 2025 01:42:17 GMT</pubDate>
            <atom:updated>2025-10-12T01:42:17.788Z</atom:updated>
            <content:encoded><![CDATA[<h3>Claude Code Max Plan vs Cursor Ultra Plan — Why Claude’s Max Plan Wins by a Mile</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1kRjVaz58eMWcW4VjyNy1g.jpeg" /></figure><p>For the past few weeks, I decided to run a real-world test between <strong>Claude Code ($200 Maximum Plan)</strong> and <strong>Cursor Ultra Plan ($200/month)</strong> — both promising AI coding copilots aimed at professional developers.</p><p>At first glance, these two might look similar. Both integrate with your IDE, both promise “infinite context” and “deep reasoning,” and both use Anthropic’s <strong>Claude Sonnet 4.5</strong> model as their flagship engine.</p><p>But after a full week of development on both platforms, the difference was <em>night and day.</em></p><h3>1. Usage Efficiency: Claude Code barely sips credits, Cursor burns them fast</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-oZs5zxzOW794Gsb9_8vkA.png" /><figcaption><em>Credit usage in Cursor after two hours of work</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*6rnwr1EBSuSQ3zelxSZh8w.png" /><figcaption><em>Claude Code credit usage after working full-time for 7 days on three heavy projects</em></figcaption></figure><p>While using <strong>Cursor</strong>, I noticed something shocking — simply working on a medium-sized full-stack project consumed around <strong>$20 worth of credits per day.</strong></p><p>That means even with the Ultra Plan, which costs $200 per month, I was close to hitting the usage ceiling in <strong>under 10 days.</strong></p><p>On the other hand, <strong>Claude Code</strong> handled the same workload gracefully.<br> After one week of identical coding sessions, I had used only <strong>7% of my weekly usage allowance.</strong></p><p>That’s a massive efficiency gap. Claude Code delivers the same work at a fraction of the cost, meaning you can comfortably use it daily without constantly watching your quota bar.</p><h3>2. The truth about Cursor’s model variety — quantity over quality</h3><p>Cursor advertises access to multiple models — GPT-4, Claude 3, Claude Sonnet 4.5, and even some “Thinking” variants.<br> It sounds impressive, but here’s the reality:</p><p>Almost <strong>every non-Claude model in Cursor feels painfully underwhelming.</strong><br> The outputs are inconsistent, verbose, or simply wrong. After testing them all, it became clear that the only truly usable option is <strong>Claude Sonnet 4.5 Thinking.</strong></p><p>Unfortunately, that’s also the most expensive one.<br> If you stick to Sonnet 4.5 Thinking — which you’ll probably have to if you care about quality — you’ll <strong>burn through the Ultra Plan in less than 10 days.</strong></p><h3>3. Credit refresh cycles: Claude Code refreshes weekly, Cursor makes you wait a month</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/813/1*a_WUQtyBTSP1Zy5o04OxlA.png" /><figcaption>Weekly Credit Recharge of Claude Code</figcaption></figure><p>Another major difference lies in <strong>how usage resets.</strong></p><p>With <strong>Claude Code</strong>, your credits <strong>refresh every week.</strong><br>That means you can push hard on a few projects, wait a few days, and get a full recharge automatically.</p><p>In <strong>Cursor</strong>, however, the usage limit refreshes only <strong>once a month.</strong><br> If you hit the ceiling early — which happens easily with Claude Sonnet 4.5 Thinking — you’re stuck waiting weeks before your quota resets.</p><p>This delay kills workflow continuity.<br> For developers working on large or ongoing projects, that’s a serious deal-breaker.</p><h3>4. Overall Experience: Claude Code feels built for professionals</h3><p>Beyond usage efficiency, the <strong>experience itself feels more stable</strong> on Claude Code.<br> Its context handling, reasoning depth, and code understanding are simply cleaner.</p><p>Cursor tries to do everything — snippets, debugging, multi-agent features — but too often, it feels like quantity over refinement.<br> Claude Code, in contrast, focuses purely on delivering <strong>deep, consistent, high-context coding assistance</strong>, which is exactly what professionals need.</p><h3>5. Verdict: Claude Code $200 plan is the clear winner</h3><p>After testing both platforms intensively, the results are clear:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ifHf1Ehi0QQZQnUHe_xSXg.png" /><figcaption>Comparing Claude Code vs Cursor</figcaption></figure><p>In short, <strong>Claude Code gives you reliability, consistency, and better usage economics.</strong><br> Cursor might look richer on paper, but when the dust settles, the Claude Code $200 plan simply delivers more usable power — week after week.</p><p><strong>Final Thoughts</strong></p><p>Cursor is an exciting idea, but it’s stuck in an awkward balance between being a playground and a pro tool.<br>Claude Code, on the other hand, feels like a platform built with professionals in mind — efficient, consistent, and refreshingly predictable.</p><p>If you’re spending $200 a month for an AI coding assistant, make it one that lasts the full month — not just the first 10 days.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a79d911cbc8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Left Stranded by Upwork: A Client’s Perspective on Freelancing Risks]]></title>
            <link>https://medium.com/@lavendarsolution/left-stranded-by-upwork-a-clients-perspective-on-freelancing-risks-06698518e456?source=rss-04bf72694b60------2</link>
            <guid isPermaLink="false">https://medium.com/p/06698518e456</guid>
            <category><![CDATA[upwork]]></category>
            <category><![CDATA[upwork-job]]></category>
            <category><![CDATA[freelancing-risk]]></category>
            <category><![CDATA[freelancers]]></category>
            <dc:creator><![CDATA[Lavendar Solution]]></dc:creator>
            <pubDate>Mon, 21 Apr 2025 23:32:51 GMT</pubDate>
            <atom:updated>2025-04-21T23:32:51.599Z</atom:updated>
            <content:encoded><![CDATA[<p>As someone who regularly relies on freelance platforms like Upwork to complete projects efficiently, I’ve always trusted these services to provide stability, fairness, and protection for both clients and freelancers. Recently, however, my experience dramatically altered my perception.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_KYWiUIHyuvWKqy3" /><figcaption>Photo by <a href="https://unsplash.com/@loicleray?utm_source=medium&amp;utm_medium=referral">Loic Leray</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>A Promising Start Gone Wrong</h3><p>My project began smoothly: clear objectives, an experienced freelancer selected, and a mutually agreed-upon fixed-price contract. I felt assured by Upwork’s reputation and safety measures.</p><p>Yet, midway through, everything collapsed. Upwork abruptly suspended my freelancer’s account without prior notice or explanation. Suddenly, I was left holding an incomplete project with no direct way to communicate or resolve issues with the freelancer.</p><h3>Forced into a Lose-Lose Situation</h3><p>Reaching out to Upwork support offered no comfort. The response was frustratingly simple:</p><p>“The funds were already withdrawn by the freelancer; there’s nothing we can return.”</p><p>Effectively, this meant:</p><ul><li>My budget was spent with no completed deliverable.</li><li>I had to allocate new resources to hire another freelancer.</li><li>Valuable time was wasted as I had to onboard a new freelancer and explain the entire project again from scratch.</li></ul><p>In short, due to an action entirely outside my control, I bore all the losses.</p><h3>Whose Responsibility Is It Anyway?</h3><p>When I challenged Upwork’s stance, emphasizing their direct responsibility for suspending the freelancer’s account, the reply remained dismissive, reinforcing that the financial responsibility and project disruption were solely mine to bear.</p><p>This scenario raises critical ethical and practical questions:</p><ul><li>How can clients trust a platform that holds unilateral power to disrupt ongoing projects?</li><li>Why doesn’t Upwork offer protective mechanisms for clients when actions taken by Upwork itself directly cause project failures?</li><li>Is the client supposed to absorb the financial and operational fallout every time a freelancer’s account gets unexpectedly suspended?</li></ul><h3>Rethinking Trust</h3><p>This experience has severely impacted my trust in freelance platforms. The relationship between clients and freelancers depends on transparency and mutual protection — values seemingly absent in this incident.</p><h3>A Necessary Change</h3><p>Upwork and similar platforms must reconsider their policies to protect their clients adequately. Without clear guarantees and accountability, clients risk losing more than just money; they risk their faith in the entire freelancing ecosystem.</p><p>I share this experience publicly because improvements can only arise from honest conversations.</p><p>Clients deserve better assurances, fairer treatment, and genuine accountability from the platforms they trust with their critical projects.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=06698518e456" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>