How I Used Claude to Land Enterprise Clients in 90 Days

I landed three enterprise clients in four months running a one-person real estate consultancy from Madeira. No sales team. No PR agency. No LinkedIn ads. Just me, a clear strategy, and Claude doing a significant chunk of the heavy lifting. When I tell other solopreneurs this, the first question is always the same: “How did you compete with agencies that have entire business development departments?” The honest answer is that I stopped trying to compete on volume and started competing on quality — and Claude made that quality achievable at a pace I could actually sustain alone.

This is the full case study. The context, the exact process, the results with numbers, and the things I’d do differently if I started over today.

Why Enterprise Clients Were Off My Radar (Until They Weren’t)

From 2012 through 2022, my consulting work in Madeira was almost entirely with individual buyers — mostly foreign nationals relocating from Northern Europe, looking for holiday homes or NHR tax residency properties. Good work, steady income, but every deal was singular. One person, one property, done.

In late 2024, two things shifted. First, I started getting referral inquiries from corporate relocation managers — companies moving employees to Portugal who needed someone on the ground in Madeira specifically. Second, a European hospitality group reached out about acquiring a portfolio of short-term rental properties to convert into a branded concept. That second inquiry alone was worth more in consulting fees than six months of individual buyer work.

The problem was immediate and obvious. Enterprise clients do not operate the way individual buyers do. They want structured proposals. They want market analysis reports with real data. They want follow-up communications that feel like they came from a firm, not a freelancer typing on a terrace in Funchal. I was not equipped for that — not in terms of time, and honestly not in terms of presentation.

I had been using Claude since early 2023 for property descriptions and client emails. But this was different. This was me asking Claude to help me look and operate like a company when I was, very much, not one.

What I Actually Tried First (and What Failed)

My first instinct was to use Claude to write a generic capabilities deck — essentially a PDF about my services dressed up with some market statistics. I spent about two hours prompting Claude to produce this. The output was fine. Technically correct, decently structured. But it read like every other consultant’s brochure. Vague value propositions. Generic claims about “local expertise.” Nothing that would make a relocation manager at a mid-size German tech company think: this is exactly the person we need.

I sent it to two prospects. Neither replied.

That was the first real lesson: Claude does not fix a bad strategy. It amplifies whatever approach you give it. Generic input produces generic output, no matter how good the underlying model is. I had to rethink what enterprise clients actually needed to see before I could use Claude effectively to produce it.

The Approach That Actually Worked: Research-First, Then Claude

I spent a week doing something I should have done first: reading. Corporate relocation RFPs, LinkedIn posts from relocation managers, case studies from international real estate firms. I wanted to understand the specific language, the specific fears, and the specific deliverables that enterprise buyers expect.

What I found was that enterprise clients — specifically relocation decision-makers and property fund managers — are not buying “local expertise.” They are buying risk reduction. They want documentation, clear process, trackable deliverables, and evidence that you have handled complexity before. They want to be able to show their internal stakeholders a paper trail that justifies hiring you.

Once I understood that, I rebuilt my Claude workflow from scratch around three specific deliverables:

1. Tailored market analysis reports — specific to the client’s sector and property use case, not generic Madeira market overviews
2. Structured capability proposals — written in the language of their industry, addressing their specific risks and timeline requirements
3. Follow-up sequences — professional, timed, and written to match the tone of whoever I was communicating with

How I Built the Market Analysis Reports

I would gather the raw data myself — transaction records from the Madeira property registry, rental yield data from short-term rental analytics tools, planning permission records, comparable sale prices from my own database. That part cannot be outsourced to Claude. Claude does not have access to hyperlocal Madeira data that lives in Portuguese government databases and my own files.

What Claude did was transform that raw data into a structured, readable report. I would paste in my data points, give Claude the context about the client (a hospitality group looking at 8-15 properties for branded short-stay conversion, for example), and prompt it to produce a report structured around executive summary, market conditions, risk factors, opportunity analysis, and recommended next steps. The prompt I settled on was detailed — about 400 words of context and instructions — and I refined it over six reports until the output required minimal editing.

Each report was 1,200–1,800 words in the final version. Before Claude, a report like that took me a full day. With the workflow I built, it took about 90 minutes: 45 minutes gathering and organizing the data, 30 minutes prompting and editing the Claude output, 15 minutes formatting in my template.

How I Wrote Proposals That Felt Like They Came From a Firm

This is where Claude’s writing quality genuinely matters. I gave Claude the company’s public information — their website, any press releases, their stated expansion strategy — and asked it to help me write a proposal that directly addressed their situation rather than describing my services in the abstract.

The key instruction I gave every time: “Do not describe what I do. Describe what they get and what problem it solves for them specifically.” That reframe made a significant difference. Proposals went from sounding like a CV to sounding like a solution document.

I also used Claude to match tone. If a company’s communications were formal and technical, I fed Claude examples of their language and asked it to match that register. If they were more casual and direct, same process. Enterprise clients notice when your communication style is jarring against theirs. It signals that you have not actually paid attention to them.

My Real-World Experience: 4 Months, 3 Enterprise Clients, One Person

Let me be specific about what this looked like from January through April 2026.

I had six active enterprise prospects in my pipeline at any point — three corporate relocation managers and three property investment or hospitality groups. Each required different communication cadences and different types of documentation. Without Claude, maintaining that pipeline alongside my ongoing individual client work would have been flatly impossible. I know this because I tried it briefly without AI support in late 2024 and watched two warm leads go cold because I was too slow to follow up with the documentation they needed.

From January to April 2026, I produced:

• 6 tailored market analysis reports (averaging 1,400 words each)
• 6 structured capability proposals
• Approximately 40 follow-up emails across the six prospects
• 3 post-meeting summary documents that recapped discussions and outlined next steps

Pre-Claude, producing that volume of high-quality written material while also running my active client work would have required at least 60–70 hours. My estimate for the same output with my established Claude workflow: 18–22 hours. That difference — roughly 45 to 50 hours over four months — is what made the whole enterprise client strategy viable for a one-person operation.

The three clients I landed: one corporate relocation contract covering 12 employee relocations to Madeira over 18 months (ongoing consulting fees), one portfolio acquisition assignment for a hospitality group looking at 6 properties, and one retained advisory arrangement with a family office based in Amsterdam that periodically acquires Portuguese real estate. The combined value of those three engagements over 2026 is roughly €38,000 in consulting fees — more than I had ever earned from enterprise clients in a single year before.

The specific moment I knew the approach was working: the relocation manager at the German tech company told me during our second call that my proposal was “more thorough than what we received from two agencies we also approached.” She was not saying I was cheaper. She was saying the document itself — the specificity of it, the way it addressed their particular employee profile and timeline — signaled that I understood their problem. Claude helped me write that document in about 2.5 hours total, including two rounds of revision.

One more honest note on the process: the post-meeting summary documents turned out to be unexpectedly powerful. After every discovery call, I would spend 10 minutes writing rough notes, paste them into Claude with a prompt to produce a clean, professional summary with action items and a restatement of what I understood their needs to be. Then I would send that document to the prospect within 2 hours of the call. Three different prospects commented on this unprompted. One hospitality group contact said it was “unusually organized” for an independent consultant. That document, which took me about 20 minutes to produce with Claude, was doing significant trust-building work.

Where Claude Fell Short: The Honest Part

Claude is not uniformly excellent at everything I tried to use it for in this process.

The biggest limitation I ran into was financial modeling language. Two of my prospects wanted proposals that included rough ROI projections or yield analysis framing. When I asked Claude to help me write those sections, the output was technically structured but often hedged to the point of being useless. Phrases like “returns may vary based on market conditions” appearing four times in two paragraphs. I understand why — Claude is appropriately cautious about financial projections — but it meant I had to write those sections myself every time. That is fine, but it is worth knowing upfront if you are in a sector where numbers-based projections are part of your sales documents.

The second limitation: Claude cannot research the prospect for you. I made the mistake early on of asking Claude to “research this company and help me personalize this proposal” with just a company name. The output was generic and, in one case, slightly outdated because Claude’s training data has a cutoff. I had to switch to doing my own research — LinkedIn, company press releases, news mentions — and feeding that information to Claude rather than expecting it to find it. Once I adjusted my process to account for this, the quality improved dramatically. But it added research time I had not initially budgeted for.

The Workflow, Step by Step

Here is exactly what I do now when a new enterprise prospect enters my pipeline:

Stage	My Task	Claude’s Role	Time
Initial Research	Read company website, LinkedIn, recent news	None — I do this manually	30–45 min
Discovery Email	Write bullet notes on their situation and my questions	Draft a professional, specific outreach email	20 min
Market Report	Gather local data from my sources	Structure and write the report from my data	90 min total
Proposal	Define their problem and my solution in bullet form	Write the full proposal document	2–2.5 hours
Post-Call Summary	Take rough notes during the call	Convert notes into clean summary + action items	20 min
Follow-Up Sequence	Define timing and key points to hit	Write 3–4 follow-up emails with varied angles	30 min

What I’d Do Differently If I Started This in 2026

Three things I would change:

Start with the post-meeting summary habit immediately. I added this about six weeks into the process after a prospect mentioned it. It should be the first thing any solopreneur adds to their enterprise client process. The effort-to-trust-building ratio is absurdly good.

Build a prompt library from day one. My best prompts — the ones that consistently produce good reports and proposals — took weeks of refinement. I now save these in a Notion database. If I had started with that discipline, I would have saved at least 4–5 hours of iterative prompting in the early weeks.

Use Claude’s Projects feature earlier. Claude’s Projects allow you to maintain context across conversations. I started using it to keep client-specific background information — their company profile, their stated goals, previous communications — available without re-pasting every session. That alone probably saves me 15–20 minutes per active client per week at this point.

The Practical Summary

Running a one-person operation and winning enterprise clients is not about pretending to be a bigger company than you are. It is about producing the quality of documentation and communication that enterprise buyers need to feel confident in their decision. Claude makes that quality achievable at the pace a solo operator can actually sustain.

The approach works because it is honest about what Claude can and cannot do. It cannot replace your domain expertise or your local market knowledge. It cannot research prospects for you. It cannot write credible financial projections without heavy editing. But it can take your knowledge and your research and turn it into polished, professional documents that would otherwise take you days — in the time you actually have between client calls.

The cost of Claude Pro in 2026 is $20/month. The first enterprise client I landed covered that cost for approximately 80 years. That is not an argument for the tool being magic. It is an argument for being specific about where you use it and why.

If you are a solopreneur trying to move upmarket and you are spending hours on proposals that are not converting, start with the post-call summary and the tailored market report. Get those two right first. The rest builds from there.

If you want to see the exact prompt structure I use for my market analysis reports, I break it down in detail in my free workflow guide — grab it here and you can adapt it to your own sector in about 30 minutes.