checkGetting Better Answers

The quality of what you get out depends on what you put in. A few simple habits make a real difference.

Lana is capable, but she's not a mind reader. The contractors who get the most from AI aren't doing anything complicated. They're just specific about what they need.


Be Specific

The more context you provide, the better the output.

Vague Request
Specific Request

"Write me an email"

"Write an email to a residential client explaining their irrigation repair is delayed two days because we're waiting on a part"

"Help me with a job posting"

"Help me write a job posting for a crew lead position. We're in Phoenix, pay $24-28/hour, and need someone with 3+ years of landscape maintenance experience"

"What should I do about this?"

"A crew member showed up late for the third time this month. What's a fair way to handle this?"

Specific doesn't mean long. It means including the details that matter: who, what, why, how much, what constraints.


Include Context

Lana knows the LeanScaper OS and has expertise built for landscape contractors. She learns YOUR business from LeanDocs and Files. But she doesn't know what you're looking at right now unless you tell her.

Good context looks like:

  • "I'm preparing for a client meeting tomorrow with the Hendersons. They've been customers for 3 years and we maintain their commercial property on 5th Ave."

  • "We're a 4-crew operation in Phoenix. Our peak season runs March through June."

  • "This is for a job posting on Indeed. We pay $22-28/hour depending on experience."

You don't need to repeat yourself within a conversation. Lana remembers what you've said. But when you start a new chat, assume she's starting fresh.


Iterate

Your first prompt rarely produces perfection. That's normal.

AI conversations are designed to be back-and-forth. The magic happens in the refinement.

Useful follow-ups:

  • "Make it shorter"

  • "More professional"

  • "Less formal, more conversational"

  • "Add a section about warranty"

  • "Actually, make it for a commercial client instead"

  • "Can you give me three options?"

Don't settle for the first response if it's not quite right. Push back. Refine. The conversation is the work.


Tell Lana Where to Look

If you've built up your knowledge base, help Lana find the right context.

Instead of: "What's our policy on this?"

Try: "Check my employee handbook for our attendance policy."

Instead of: "Help me write this like we usually do."

Try: "Use the tone from my client communication templates."

Lana searches your LeanDocs and Files, but being specific about where to look gets better results.


Show Examples of "Good"

When you want output that matches a specific style or format, show Lana what good looks like.

  • "Here's an email we sent last month that worked well. Write something similar for this situation."

  • "This is how we usually structure job descriptions. Follow this format."

  • "Our brand voice is friendly but professional. Like this example."

Examples do more than descriptions. If you have templates or past work that represents your standard, reference them.


Common Patterns

Thinking Through Problems

Lana can help you think, not just write. Use her as a sounding board.

Try:

  • "I'm deciding between X and Y. What are the tradeoffs?"

  • "What am I not considering here?"

  • "Play devil's advocate on this plan."

  • "What would an experienced operations manager say about this approach?"


When Lana Gets It Wrong

Lana makes mistakes. When she does:

  • Correct her directly: "That's not quite right. We actually do X."

  • Add context she was missing: "I should have mentioned that this client is price-sensitive."

  • Ask her to try again: "Take another approach. That one doesn't work for us."

Don't assume the first answer is the best answer. Lana can course-correct when you give her feedback.

circle-exclamation

Last updated

Was this helpful?