A Gap Worth Watching
A funding round puts a company at the center of a conversation. The customer, though, may never have read the announcement. They open the app, look for what they need, and decide whether it's worth coming back. That gap between the public announcement and the individual experience interests me more than the celebratory photo. It's in that gap that a promise of growth starts to meet the concrete reality of the people who are supposed to sustain it.
Lince Capital announced an investment in Erakulis, a Portuguese wellness platform whose shareholders include Cristiano Ronaldo. The investor frames technological development and international expansion as the intended destinations for the funds. That announcement documents a financing decision. It does not, on its own, reveal customer satisfaction, retention, or profitability in any given market. What follows is a reflection on management, not an assessment of those indicators at Erakulis specifically.
The Responsibility That Follows the Check
I see a particular responsibility in the period right after capital comes in. Conditions emerge to hire, experiment, and fix limitations. At the same time, pressure builds to show movement. More countries, more features, more campaigns. None of that is necessarily a mistake. The difficulty lies in telling which of these initiatives brings the company closer to the kind of use it wants to make valuable, and which simply produces activity that's easy to show off in a meeting.
Imagine a fictional company selling a subscription to organize household chores. A campaign brings in plenty of sign-ups, but a chunk of those people stop using the service after the first week. The team might read the drop-off as a lack of visibility and buy more advertising. Or they might discover that the first encounter with the product requires too long a setup. These two hypotheses lead to different decisions, even though both could be filed under the word growth.
Reconstructing the Path Before Choosing
Before choosing, I would want to reconstruct the journey. What did the person expect to solve? At what point did they manage to do it? Where did they need help? The silence of someone who leaves also deserves attention, but it doesn't give the company license to invent a reason for them. A voluntary conversation, an observable difficulty, and a repeated pattern offer distinct kinds of evidence. Bringing them together carefully is more useful than turning a single impression into a truth about the entire customer base.
I'm not suggesting every decision wait for an endless investigation. I'm suggesting an explicit relationship between doubt, test, and consequence. If the hypothesis is that onboarding drives people away, a limited change to that journey gets tried. What counts as a favorable signal, and for how long it will be observed, gets defined beforehand. If the result contradicts the expectation, the team should be able to say so without fearing that honesty will cost it credibility.
What Leadership Rewards, Teams Will Produce
This possibility depends on leadership. A leader who praises only rising numbers quickly teaches everyone else to select for rising numbers. They may receive flawless presentations while losing track of the real experience behind them. I'd rather sit in a meeting where someone lays out a specific difficulty and asks for a concrete decision. The discomfort lasts a few minutes; the correction can save months of work aimed at the wrong explanation.
Translation Is Not Adaptation
Entering a new market brings another temptation: treating translation as if it were full adaptation. A sentence can be linguistically correct and still promise something the local operation can't deliver. Service hours, payment methods, expectations around support, and the way value gets presented all need to be understood on their own terms. That doesn't license generalizing an entire country from a couple of interviews, but it does stop headquarters from mistaking its own familiarity for universal knowledge.
Sales hears objections; customer support sees friction points; the product team knows the technical dependencies. If those conversations stay siloed, an organization can make the same discovery three times without ever turning it into a change. It falls to management to create a decision point where these threads meet. It doesn't need to be a heavy ritual. It needs to be clear who decides, with what information, and how the decision makes its way back to the people affected by it.
The Trouble With Comparing Averages
There's also a care to take with comparisons. Customers who arrived through a referral may behave differently from those drawn in by a promotion. An improvement in the average can come from the composition of the group, not from the change that was just launched. That problem doesn't get solved with a fancier word in the report. It gets solved by keeping track of the context behind an observation and being honest about how much of a difference can actually be attributed to the intervention.
The same caution applies to timing. A first use might show that access got simpler. It doesn't yet show that the person found a reason to come back the following month. Management needs to accept that different things take different amounts of time to learn, without turning that into an excuse for never deciding anything. Some decisions can move forward right away; others require watching a full cycle play out. Telling the two apart helps put capital to use with purpose.
Leaving Room for What Isn't Explained Yet
I would set aside space for what still isn't explained. A report can hold the provisional conclusion, the evidence behind it, and the observation that would force a revision. That last part matters most: it makes it possible to change direction without pretending the original intention was always something else. It also protects the team from defending an initiative simply because it already poured work and reputation into it.
Preparing for the Next Ordinary Moment
A funding celebration has its place. People put in the time, took on responsibility, and secured the resources to keep going. Honoring that effort doesn't require treating the financing as advance proof of everything still to come. If anything, it can open space for a more grown-up conversation about priorities, execution capacity, and the difficulties that need solving before anyone accelerates.
To me, Resolutive Intelligence shows up in that passage from ambition to a testable choice. The company names the problem it wants to solve, listens to the people living through the journey, tests a response, and owns what it learns. Capital gives it possibilities. The customer will keep judging the outcome the next time they need the service. It's for that far less ceremonial moment that the organization is worth preparing.