Why I no longer accept projects without an initial analysis: the method I have developed over the years

For years, I started from the wrong point.

When I look back at my early years in digital marketing, I realize that I often started with the same question my clients asked me: “I need a new website,” “I want to be first on Google,” “I need more followers,” “We need to run an ad campaign.” The conversation almost always began with the solution the client had already imagined, and like many professionals, I would immediately start working on that request.

It seemed like a logical way to work. The client expressed a need, and I would look for the most suitable tool to satisfy it. Over time, however, I realized that this starting point was almost always wrong because the requested solution rarely matches the real problem. A new website can be useless if the company’s positioning is unclear. An ad campaign can bring in traffic without results if the offer isn’t clear. Investing in social can increase visibility without improving reputation, sales, or the quality of inquiries.

It was by observing different projects, especially in tourism, food, hospitality, and communication, that I changed my method. I stopped accepting the solution as the starting point and began working on the problem. Today, before talking about tools, channels, content, or campaigns, I try to understand what isn’t working, why it isn’t working, and what goal the company truly wants to achieve. I no longer start from the answer. I start from the questions.

The client almost always arrives with a ready-made solution.

It’s understandable that an entrepreneur or professional comes to a consultant with a pre-formed idea. They’ve observed competitors, read a few articles, seen a campaign they liked, or received advice. Maybe they think the problem is the website, because the competitor’s site looks more modern. Or they believe they need TikTok because everyone’s talking about it. Or maybe they want to invest in SEO because traffic has dropped.

The point isn’t to say these insights are always wrong. In many cases, they can be correct. The problem arises when these are treated as diagnoses, when they are actually just hypotheses. A serious professional shouldn’t simply confirm the client’s initial idea just to move toward a quick quote. They should check if that solution matches the problem, the market, the available resources, and the real objectives.

Many companies ask for a new website when, in reality, they need to rethink their offer. They request content when there’s no editorial strategy. They ask for visibility when the problem is credibility. They want more followers without having clarified who they are speaking to. They ask for advertising when the customer experience, from first contact to conversion, has obvious gaps.

Accepting the request without analyzing it may seem like the fastest way to start working. In reality, it often just means moving the problem further down the line, after having already spent time and money.

The initial analysis is not a formality.

When I talk about initial analysis, I’m not referring to a document filled out to justify a preliminary phase of the project. It’s not a formality, nor a way to slow down the work. It’s the moment when we determine whether what the client is asking for is really what they need.

Analysis serves to bring order. It helps to understand the market, the competitors, the audience, current reputation, active channels, published content, results achieved, and available resources. It also helps to identify contradictions: what the company claims to be, what it communicates, and what the customer perceives do not always coincide.

In many cases, the most important work happens right here. Before choosing a platform, before building an editorial plan, before investing in advertising or starting a Digital PR. Analysis allows you to distinguish what is urgent from what is important, what is a symptom from what is a cause.

This approach is valuable in every sector, but in travel and food it becomes even more evident. A hotel may have a booking problem and think the solution is a new campaign. A restaurant might ask for more visibility on social media, when the real issue is an undifferentiated positioning. A destination might invest in content without having defined an identity, an audience, or a proposal capable of turning attention into real interest.

Understanding comes before tools.

We live in a time where every problem seems to have a technological answer. New software, a more advanced platform, the latest artificial intelligence, a dashboard, an automation system. Tools are important and, in many cases, can greatly improve work. But they remain tools.

Before choosing which one to use, you need to understand what problem you’re trying to solve. It seems obvious, but it’s a step that’s continually skipped. Technology is purchased because it’s new, a channel is opened because it’s trendy, content is produced because “you have to be there.” Then, after a few months, you realize the investment hasn’t produced the desired result.

The same confusion often occurs between digitalization and strategy. Digitizing a process doesn’t automatically mean improving it. A more modern website doesn’t fix an unclear offer. A booking system doesn’t solve a trust issue. A CRM doesn’t create a relationship with clients if no one has defined what to communicate, when to do it, and with what goal.

I also covered this in the article on how to digitalize a restaurant without confusing tools and strategy. Technology can make a project more efficient, but it can’t replace initial understanding.

A well-done analysis can completely change the project.

One of the most interesting aspects of the initial analysis is that it often leads to a different conclusion than expected. The client comes in asking for a service and discovers that the real priority lies elsewhere. It doesn’t mean the initial request was useless, but rather that it lacked an overall vision.

A company may ask for a social media strategy and find out the main problem is the lack of proprietary content. They may request SEO and realize that the website pages don’t clearly explain what they offer. They may want to invest in Digital PR and realize they don’t yet have a story, data, projects, or solid enough content to approach the media. They may want more traffic and discover that the site already gets visits but can’t transform them into contacts.

This last scenario is particularly common. Traffic is often considered a goal, when it should only be part of the journey. In the article on why website traffic isn’t enough if it doesn’t generate conversions I tackled this very issue: increasing visits is pointless if you don’t understand what happens after the user enters.

The initial analysis helps avoid this short-sightedness. It doesn’t look at just a single data point, but at the entire journey. It doesn’t just look at the channel, but the system. It doesn’t just ask what to do, but why to do it and what result it should produce.

The problem isn’t always where it appears to be.

Many marketing problems are symptoms of deeper issues. A drop in sales may depend on visibility, but also on an uncompetitive offer, weakened reputation, inconsistent communication, or market change. Low social interactions might indicate ineffective content, but also the wrong audience, an impersonal tone of voice, or an identity-lacking presence.

That’s why I don’t believe in immediate diagnoses. To understand a project, you have to look at its history, context, and internal relationships. You have to read the data but also listen to people. You have to check what the company says about itself and compare it with what emerges from outside.

Sometimes the company thinks it has a communication problem, but actually has an organizational one. Or it believes there’s a product issue, when the product is solid but misunderstood. Other times, the opposite: marketing is used to patch up weaknesses that belong to the real experience.

Marketing can’t cover up what doesn’t work. It can certainly help focus on a value, tell its story, make it more visible and understandable. But if there is a gap between promise and experience, sooner or later that gap will show.

The initial phase is also a compatibility test.

Analysis is not just about understanding the project. It’s also about seeing if the conditions exist to work well together. It’s a phase where expectations, availability, limits, responsibilities, and the ability to make decisions all come to the surface.

Not every project is right for every professional, and not all clients are ready for a strategic journey. There are companies seeking real discussion, and others wanting only confirmation. There are clients open to questioning their beliefs, and those who have already decided everything and just want someone to execute.

There’s nothing wrong with executional work, as long as it’s defined as such. The problem arises when a consultant is asked to take responsibility for results without being allowed to analyze, ask questions, or suggest a different direction.

Today, I see this compatibility as essential. A good project is born out of clarity in roles. The client knows the company: the lived market, the restrictions, and internal opportunities. The consultant brings method, outside experience, analytical skills, and a perspective less influenced by habits. Value emerges when these two perspectives engage in dialogue.

I don’t sell a solution at the first meeting.

Over time, I have learned to distrust answers that come too quickly, even my own. When a project is described in a phone call or during a brief meeting, it’s easy to recognize familiar patterns and immediately imagine a solution. Experience helps, but it can also create automatic responses.

That’s why I prefer not to turn the first conversation into an immediate sale. The initial meeting is for listening, gathering information, identifying areas to delve deeper, and understanding whether what is being requested aligns with what emerges.

The client doesn’t always appreciate this caution. We are used to quick quotes, ready-made packages, standard pricing, and instant answers. But a strategic project is not a product off the shelf. Two companies in the same sector can have completely different problems. Two hotels in the same city might require opposite interventions. Two restaurants of similar size may target different audiences, positioning, and incompatible business models.

Speed is useful when the problem is clear. Before that, it’s just haste.

The questions that change the course of the work.

Every analysis starts from a few key questions, but there is no universal questionnaire that can replace reasoning. The questions change depending on the project, the sector, and the phase the company is in. Some, however, come up often.

What result does the company truly want to achieve? How is this measured today? Who is the priority customer? What problem does the offer solve? Why should someone choose this company instead of a competitor? What activities have already been tried, and with what results? What resources can be dedicated to the project? Who will make the decisions? How much time is needed to produce content, respond to contacts, handle requests, and keep promises?

These questions seem simple, but they often bring to light decisive contradictions. A company may say they want to increase leads and then have no one assigned to respond. They may want to attract a high-end clientele while communicating almost exclusively about price. They may seek authority but at the same time refuse to invest in content, relationships, or editorial quality.

Analysis also serves to make these inconsistencies visible. Not to judge, but to prevent them from becoming hidden obstacles during the project.

Method does not eliminate intuition—it makes it stronger.

Talking about analysis may make it sound like a cold process, dominated by data, tables, and procedures. In reality, my method doesn’t eliminate intuition. It puts it to the test.

Experience often allows you to quickly sense where a problem might lie. But that sense must be verified. Data helps to see whether the intuition is right, discussion with the client adds context, competitor analysis lets you distinguish an internal problem from a market dynamic.

Method, therefore, doesn’t replace creativity. It prevents it from becoming arbitrary. A good idea can be born in a few minutes, but it needs to rest on a real understanding of the project. Otherwise, it risks being brilliant, well-presented, and completely useless.

Useful content and strategic content are not the same thing.

This approach also applies when the project involves content. Many companies request a blog, an editorial calendar, or greater presence on social media resources, but haven’t defined what role that content should serve.

A piece of content can be useful and well written without contributing to the company’s goals. It may inform, entertain, or drive traffic, but not strengthen positioning, reputation, or the acquisition process. In the article on the difference between useful content and strategic content I explained why editorial quality alone is not enough.

Here too, the initial analysis changes everything. Before producing content, you need to understand which questions the brand must answer, which topics it should own, which perception it wants to create, and what action it wants the reader to take. Without this step, the editorial calendar can become just an orderly sequence of posts with no direction.

Accepting everything doesn’t mean working better

For a long time, I thought that being available meant always finding a way to respond to requests. Today, I consider this availability useful only when it doesn’t compromise the quality of the work. Accepting a project without being able to analyze it, without access to the necessary information, or without the possibility of questioning the request is not flexibility. It’s a risk for both parties.

The client risks investing in an ineffective solution. The professional risks becoming responsible for results that depend on decisions made without their input. In the end, even technically correct work can be perceived as a failure.

That’s why today I prefer to turn down a project when I’m asked to start straight from execution without understanding the bigger picture. It’s not a rigid stance. It’s a form of responsibility. Saying yes to everything may seem convenient in the short term, but it often leads to fragile relationships, unrealistic expectations, and results that are hard to defend.

The initial analysis has its own value

Another important step in my method is recognizing that analysis is neither a free nor an accessory activity. It is work. It requires time, skills, the ability to interpret, compare, research, and synthesize. Above all, it generates independent value: it helps the company better understand its situation, even before deciding which activities to implement.

In the past, analysis was often lumped into the general quote, as if it were an inevitable preliminary step but lacking its own identity. Today, I prefer to treat it as a distinct phase, with clear objectives, materials, and conclusions. It can lead to a larger project, but it doesn’t have to exist solely as a step toward the following sale.

This also changes the relationship with the client. Analysis no longer becomes a free demonstration aimed at convincing them, but rather a shared effort to understand the situation and make more informed decisions.

The method I’ve developed over the years

My method today starts with listening, continues with gathering information, and reaches the definition of priorities. I don’t immediately look for the most suitable channel. I look for the knot to untangle.

I analyze positioning, existing communication, content, digital presence, reputation, competitors, available data, and the coherence between objectives and resources. I also evaluate what isn’t visible online: the sales process, the ability to manage contacts, the quality of the experience, the relationship between what is promised and what is actually delivered.

Only after this phase does it make sense to build a strategy. Sometimes the solution will be a new website. Other times, it will be work on content, PR, SEO, positioning, reputation, or channel organization. In some cases, the best choice will be not to launch any campaign right away and instead spend time correcting deeper issues.

It’s not a spectacular method. It doesn’t promise instant results or lend itself to catchy slogans. But it’s the most honest way I’ve found to tackle complex projects without confusing activities with strategy.

Conclusion: every project needs a map

Today, I don’t reject a project because it’s small or large, simple or ambitious. I turn it down when I’m asked to start from the solution without understanding the problem. Because marketing isn’t a list of services to purchase. It’s a journey to be built.

Initial analysis doesn’t guarantee that everything will be easy, nor does it eliminate every margin of error. However, it allows you to make more informed choices, set realistic priorities, and use tools and resources with a clear direction.

Over the years, I’ve learned that an effective strategy rarely comes from the quickest answer. It comes from the right question, asked at the right time, and from the willingness to challenge what seemed already decided.

Every journey, before it starts, needs a map. Today, that’s where my work begins.

To further explore a project before choosing tools and activities, you can request an initial consultation and start with a concrete analysis of objectives, critical issues, and priorities.