🤝 Consulting Delivery & Business

An effective proposal starts with the outcome the client wants — lower costs, more revenue, less risk — and only then describes how you’ll get there. It doesn’t start with hours or activities.

A proposal based on hours puts consultant and client in a cost game; a proposal based on outcomes puts them on the same side of the table.

Results first; hours are a consequence; the proposal is an alignment document, not a quote.

Scope is what you deliver; out of scope is what you explicitly don’t deliver. Both sections need to be in the proposal—out of scope is where most conflicts begin.

Silent scope creep is the biggest enemy of profitability. Clear boundaries protect you and the client.

A written scope protects you; explicitly define what’s out of scope; scope changes = new negotiation.

Dividing the engagement into phases with clear milestones creates natural checkpoints where the client and consultant assess whether continuing makes sense — and creates opportunities to expand the scope.

Phases reduce the client’s perceived risk, make project approval easier, and create opportunities to renew the relationship.

Assessment → plan → execution; milestones create visibility; a checkpoint is an opportunity to expand.

The proposal should list what the client needs to provide: data access, stakeholder participation, validation meetings, and timely decisions. The consultant delivers better when the client does their part.

Projects fail when the client disappears. Making client expectations clear upfront prevents delays and conflict.

Shared responsibilities; the client as an active partner; prerequisites listed in the proposal.

The Statement of Work (SOW) formalizes what will be delivered, when, and how it will be accepted. Acceptance criteria are objective: “report approved at a review meeting” is clearer than “client satisfied.”

Without objective criteria, the project never ends—the client always has "one more thing." The SOW sets a clear endpoint.

SOW as a lightweight contract; objective acceptance criteria; "done" has a written definition.

An impossible scope, an absent sponsor, a client who wants results without involvement, or a price that doesn’t cover the cost of the relationship are signs that turning down the project protects your reputation and energy.

Bad projects cost more than the money they bring in: they drain energy, send the wrong signals to the market, and block good projects.

Client red flags; hidden costs of a bad project; saying no also builds your reputation.

Hourly pricing is easy to calculate, but it penalizes consultants who get faster and more efficient. The better you get, the less you earn — the logic is backwards.

Recognizing the natural ceiling of the hourly model motivates you to seek models that decouple income from hours worked.

Hourly cap; efficiency penalty; hourly billing makes sense for projects with undefined scope or ad hoc support.

Fixed-scope package with a fixed price. The client knows what they pay; you know what you deliver. When you become more efficient, profits rise without needing to renegotiate.

It’s the most common model for assessments and diagnostics—and the first step toward decoupling time from income.

Mutual predictability; fixed scope required; productivity becomes profit.

A retainer is a fixed monthly fee for the consultant’s availability and ongoing attention. It creates predictable revenue, an ongoing relationship, and makes it easier to expand the scope over time.

Recurring revenue is the long-term goal: you stop starting from scratch every month and have a foundation for planning your practice.

Availability, not hours; ongoing engagement; a foundation for natural scope expansion.

The price is based on the value generated for the client, not the time spent. If you identify R$500k in savings, charging R$50k for that is reasonable — regardless of how many hours it took.

It’s the model that best aligns incentives: you want the client to succeed because that’s what justifies the price.

Price × impact; ROI anchoring; requires a solid diagnostic to quantify value.

Each step on the ladder solves a different problem and prepares the next engagement. The assessment diagnoses; the plan prioritizes; the execution delivers. It’s a natural progression of trust.

The ladder turns the first small contract into a gateway to larger contracts—without having to sell complex projects right away.

Start with low risk; build trust; each deliverable sells the next.

A paid assessment is an offering with a small scope, an accessible price, and a concrete deliverable — usually a priorities report. It filters for serious clients and funds the assessment that comes before every recommendation.

A free assessment creates the expectation that diagnosis has zero value — distorting the relationship before it even begins.

Assessment as a product; a seriousness filter; a concrete deliverable justifies the payment.

A structured form sent before the first meeting to map data, process, and culture maturity. You arrive informed and save hours on basic discovery.

You come into the conversation with formed hypotheses — and demonstrate a level of professionalism that already sets you apart from most consultants.

Pre-work; hypotheses before the meeting; template reused with all clients.

The map lists all identified use cases; the matrix places each one in a quadrant based on high/low value × high/low feasibility. The "high value, high feasibility" quadrant is where you start.

Shifts the conversation from “AI everywhere” to “we’ll start with the two or three cases with the most impact and the least friction.”

Quick wins first; matrix as an alignment tool; shared visibility.

Waves group cases by time frame—wave 1 (90 days), wave 2 (6 months), wave 3 (12 months). The one-page business case summarizes the problem, solution, ROI, and risks for each wave.

Executives approve projects that fit on one page. Anything more is bureaucracy that delays decisions.

Waves as a sequence; business case ≤ 1 page; ROI clear to non-technical readers.

A one-page document covering the current situation, identified opportunity, proposed approach, and expected outcome. It speaks the C-level’s language without needing to open a 40-slide presentation.

Decision-makers read at email speed. The one-pager increases the approval rate because it removes the friction of processing dense information.

Situation → opportunity → approach → result; business language; no more than one page.

The risk register lists what could go wrong, the likelihood, the impact, and the mitigation. The governance note documents who decides what. Both protect the consultant and the client from surprises.

AI projects have specific risks—bias, privacy, silent failures. Documenting them upfront is more professional and less expensive than dealing with them later.

Risk mapped in advance; clear governance; documented accountability.

Each deliverable you create from scratch for a client can become a template for the next one. Productizing means turning custom work into a reusable foundation that accelerates future projects.

The difference between a consultant who works hard and a scalable practice lies in reusable assets. Templates are the lever that multiplies your capacity without multiplying your hours.

Template as an asset; the first client funds the template; each project improves the collection.

Most AI projects fail in adoption, not development. The technology is ready, but people keep using the old processes—and the expected results never appear.

Recognizing the real bottleneck changes the focus: you don’t just deliver the product—you deliver the outcome, which includes ensuring the product is used.

Adoption ≠ deployment; results require use; delivery includes behavior change.

A sponsor is someone with the authority and interest to ensure success; champions are enthusiastic users who influence their peers. Training in the workflow means teaching the tool as part of the actual task, not in isolated classrooms.

Without a sponsor, the change dies at the first priority conflict. Without champions, there’s no positive contagion across the team.

The trio: sponsor + champion + contextual training; internal momentum accelerates adoption.

Define adoption metrics (usage rate, frequency, active users) and value metrics (time saved, errors reduced, revenue generated) before the project — and revisit them 30, 60, and 90 days after launch.

The post-delivery follow-up is the moment to demonstrate value, identify what didn’t stick, and start a conversation about the next step. It’s the seed of a long-term relationship.

Metrics defined in advance; revisit at 30/60/90 days; post-delivery follow-up opens the door to the next contract.

Being an AI consultant for any company is hard to sell. Being the AI consultant for medical clinics or e-commerce logistics is specific enough to be remembered and recommended.

A niche lowers customer acquisition costs: people know each other within an industry, referrals spread quickly, and accumulated knowledge becomes a barrier to entry.

Specialization builds authority; referrals circulate within the niche; accumulated knowledge is an advantage.

When a project requires technical execution beyond your focus, partnerships with implementers or subcontractors let you take on larger projects without expanding your internal team.

Orchestration matters more than execution. Knowing when to outsource and how to maintain quality is what distinguishes a consultant from a freelancer.

The consultant orchestrates; the partner executes; you remain responsible for quality control.

The project ends, but the relationship doesn’t. Clients who trust the consultant keep coming back — for new projects, to validate decisions, and to make referrals. The relationship is the real asset.

Acquiring a new customer costs much more than retaining one who already trusts you. Sustainable practice is built on relationships, not constant prospecting.

Compound trust; retention > acquisition; the relationship is the long-term product.