Answers to the questions organizations ask us most.

upMention helps organizations identify, select and execute their growth potential. We combine commercial intelligence, strategy, marketing and technology, but only deploy what the chosen direction requires.

Sometimes that means SEO, GEO or online advertising on its own. Sometimes software development through DaaS is the right step. And sometimes the visible marketing issue is a symptom of something else, such as an unclear proposition, weak follow up, stalled collaboration or unclear ownership.

We use upMention Intelligence to bring together information from the organization, customers, market, results and digital channels. Our people interpret what it means and translate it into a priority, roadmap, execution and measurable result.

You can. The question is not how many services you use, but which effort contributes most to the desired result. When SEO, GEO, online advertising or DaaS on its own is the right step, the collaboration remains fully focused on that discipline.

Even with one discipline, we perform a compact check of the objective, strategy, proposition, customer journey, follow up and measurement. This prevents us from optimizing a channel while the real constraint sits somewhere else.

No. We do not sell a mandatory strategy phase. We do always perform a strategic check that matches the size and complexity of the question.

When the direction is clear and supported, we move into execution quickly. When there are contradictions or untested assumptions, we make those visible first. It would not be responsible to scale reach or software capacity without knowing that we are working on the right question.

Not automatically. More reach does not automatically make the right thing visible. Before we scale SEO, GEO or advertising, we test whether the audience, offer, positioning, proof, customer journey and commercial follow up are aligned.

When that foundation is strong, we create visibility with focus. When it is not, we first address the constraint that limits growth most. Otherwise, the wrong thing simply becomes more visible.

A broader approach is useful when the cause and symptom do not sit in the same place. For example, marketing may generate many leads while sales does not follow up, the offer may not match what customers need, or responsibilities, capacity and decision making may slow growth down.

In that case, we do not only analyze the channel. We analyze the connection between strategy, people, processes, data, market and technology. The goal is not to make the engagement larger. The goal is to find the smallest intervention that creates the greatest difference.

Yes. We can execute work in full, pick it up together with your own team, or plug into existing agencies, media partners and technical suppliers.

Upfront we make clear who owns each task, who makes decisions and who guards quality and coherence. That prevents duplicate work, confusion and separate activities that don't add up to the same result.

Yes. We start with a focused handover. We look at existing agreements, results, accounts, documentation, campaigns, ad accounts, conversion measurement, product feeds, audiences, technology, code and open work.

We then make visible what works well, where the risks sit and what needs attention first. We don't automatically replace everything that already exists.

We start with the desired result and the question of what currently stands in the way. We then determine which information is already available, which assumptions need to be tested and which people need to be involved.

The first analysis is recorded in upMention Intelligence. It leads to a clear priority, a plan for the first 30 and 90 days and, where relevant, a roadmap for 365 days. We also define ownership, capacity, measurement points and the monthly decision moment.

You can when SEO is the effort that moves the desired result closer most efficiently. You do not need to add GEO, advertising, software development or a broad strategy process.

We do first perform a compact check of the search demand, audience, proposition, website, conversion path and follow up. We then focus the collaboration completely on technical SEO, structure, content, authority, conversion and measurement.

SEO is improving your organic findability in search engines. It is not just about individual keywords or positions.

Good SEO connects search behaviour, relevant content, a clear website structure, technical accessibility, external authority and a logical next step for the visitor. Depending on the organisation the focus can be local, national or international.

We start with the baseline, relevant search questions, technical quality, website structure, existing content, authority and conversion. Based on that, we create a roadmap with the improvements expected to create the greatest effect.

The work can include technical fixes, restructuring, new and improved content, internal links, local visibility, relevant external mentions and conversion improvement. Each month, we connect execution to visibility, behavior, enquiries and commercial results.

Yes. We can not only identify what needs to improve technically, we can also implement the improvements.

Our developers can work on indexability, speed, site structure, redirects, structured data, templates, internal links, multilingual setups and technical errors. That way a technical recommendation doesn't stay stuck waiting for another party.

Yes. We can take care of research, content planning, interviews, writing, editing, publication and maintenance.

For specialist topics we like to work with the experts inside your organisation. They bring the knowledge and experience. We translate that into clear content that fits the audience's question and can be found and understood well.

We structure SEO as a collaboration that can be adjusted or ended each month. One month may focus entirely on an audit, migration or technical recovery, but the work is always connected to execution and measurement.

You are not tied to a long contract term. At the same time, we work with a roadmap so that every month contributes to a deliberate build up rather than becoming a series of isolated optimizations.

We look at the development that fits the commercial goal. That can include visibility, positions, impressions, clicks, organic traffic, local findability, requests, revenue or other valuable actions.

We record the starting point upfront and keep organic results clearly separate from paid traffic from online ads. That makes visible which channels contribute to reach, requests and commercial results.

GEO stands for Generative Engine Optimization. It focuses on visibility in AI search engines and answer environments.

The goal is for AI systems to properly understand your organisation, expertise, products and content. That increases the chance your brand is mentioned, your information is used as a source or your organisation is included in a relevant answer.

SEO focuses mainly on findability in traditional search results. GEO focuses on answers that are composed by AI systems.

There is a lot of overlap. Both need accessible technology, relevant content, clear expertise and credible external sources. GEO also asks for extra attention to clear entities, consistent facts, citable information, source attribution and the way AI systems summarise a topic.

You can when AI visibility is the right point of leverage. You do not need to add a full SEO program, advertising or a broader collaboration.

We first test whether the organization can explain clearly and credibly who it is, who it serves, which expertise it has and which evidence supports that. We then focus the collaboration on subjects, entities, sources, citable content, external authority and periodic measurement.

We first determine for which questions, subjects and decision moments the organization wants to be relevant. We then investigate how AI systems currently describe the organization, which sources they use, which competitors are mentioned and where information is missing or contradictory.

We then improve the clarity of entities, facts, expertise, evidence, content structure, technical accessibility and external mentions. We do not simply create more information. We make sure the right information becomes understandable, verifiable and citable.

We work with a fixed set of topics, questions and search intents that matter for the organisation. We remeasure them periodically.

We look at mentions, sources used, citations, answer accuracy, position versus competitors and the topics where the organisation is or isn't visible. Because AI answers can differ from moment to moment, we judge patterns and development across several measurements.

No. AI systems decide themselves which sources and organisations appear in an answer. The outcome can also differ per question, user and moment.

We can improve the information, technology, authority and external signals these systems base their answers on. We then make measurable whether visibility and source usage develop positively.

Yes. That is often efficient, because part of the technical, content and authority work reinforces each other.

It is not required. SEO, GEO and online advertising can each be run independently. When several forms of visibility need improvement, we make one coherent plan with separate goals, budgets and measurement points per part.

You can when online advertising is the most efficient next step. You do not need to add SEO, GEO, software development or a broad growth program.

Before we spend budget, we do test whether the audience, offer, message, landing page, conversion measurement and commercial follow up are aligned. A campaign can buy reach quickly, but it cannot repair a weak proposition or a stalled sales process.

Online advertising is becoming visible through paid placement in search engines, social media, video, websites and other digital environments.

It isn't just about buying ads. A good approach connects audience, message, offer, landing page, conversion measurement, budget and commercial follow-up. The goal isn't as many clicks as possible, but relevant attention that leads to a valuable next step.

We can manage campaigns on Google Ads, Microsoft Ads, LinkedIn Ads and Meta Ads, among others. YouTube campaigns can be set up through Google Ads.

We don't automatically use every platform. The choice depends on the audience, search behaviour, offer, customer journey, available budget and measurement quality.

SEO focuses on organic findability in search engines. SEA stands for paid advertising within search engines, for example through Google Ads or Microsoft Ads.

Online advertising is broader than SEA. It also covers advertising through social media, video, display and other paid channels. SEO, SEA and other forms of online advertising can be used together, but can also each be taken as a stand-alone service.

We start with the commercial objective, existing results, audience, offer, margin, customer journey, account structure, conversion measurement and follow up. We then determine which platforms, campaigns, messages and landing pages have a clear role.

We build or improve campaigns, advertisements, audiences, bids, landing pages and measurement. Results from advertising platforms, Analytics, CRM and commercial follow up are connected in upMention Intelligence where possible. This allows us to optimize not only for clicks and forms, but for the quality and value of new customers.

Yes. We start with a focused review of the account structure, access, campaigns, search terms, audiences, exclusions, ads, feeds, budgets and conversion measurement.

We then make visible what works well, where money is being lost and which parts need attention first. We don't automatically remove or replace everything that already exists.

The organisation remains the owner of its ad accounts, historical data, audiences, product feeds and other company-specific data.

Where technically possible, accounts are set up directly in the organisation's name and upMention receives the required access. That way the organisation doesn't become dependent on upMention to reach its own data or campaigns.

Yes. We can develop and improve ad copy, creative variants, forms and landing pages.

The ad and the page behind it need to create the same expectation. That's why we don't only look at the click, but also at clarity, trust, ease of use and the next step someone needs to take.

Then we first map which actions really matter and how they can be reliably measured.

That can involve forms, phone calls, purchases, appointments, downloads, quotes, qualified leads or revenue from the CRM. We don't scale campaigns based only on clicks or incomplete platform data.

We look at the commercial goal, the size of the audience, expected click prices, conversion probability, customer value, margin, working area and the amount of data needed to be able to learn.

A higher budget isn't automatically better. But a budget must be large enough to seriously test the chosen market and approach. When the available budget is too small for that, we say so upfront.

No, unless explicitly agreed otherwise in a proposal. The media budget is the amount spent directly on the advertising platforms.

The fee to upMention covers the agreed activities, such as research, setup, campaign management, creative, landing pages, measurement and reporting. Both amounts are shown separately in the proposal.

We decide upfront which outcome matters to the organisation. That can be a purchase, request, appointment, quote, qualified lead, revenue or another valuable action.

We look at media budget, reach, clicks, conversions, cost per result, quality of requests, sales opportunities, revenue, margin and return, among others. Figures from the ad platform are, where possible, connected to information from the website, CRM and commercial follow-up.

CPA stands for cost per agreed action or acquired customer. CPL stands for cost per lead. ROAS compares the measured revenue from ads with the media budget spent.

These figures are useful, but don't tell the whole story. A cheap lead can have little value and high revenue can go together with a low margin. That's why we also look at lead quality, customer value, margin and the actual commercial follow-up.

We look beyond the number of submitted forms. Together we define when a lead is suitable, reachable and commercially relevant.

Feedback from sales or the CRM is fed back into the campaigns. That way keywords, audiences, ads, forms and budgets can be adjusted based on the quality of requests, not just on volume.

No. The result also depends on market demand, competition, click prices, offer, price, website, season, sales follow-up and changes within advertising platforms.

We can work out assumptions and scenarios upfront, set up measurement properly, monitor budgets and make visible what works and what doesn't. When results lag, we investigate the cause and adjust the approach.

We do not offer SEO, GEO and online advertising as a mandatory package. We determine the role of each channel in the customer journey and the additional effect it can provide.

Advertising can create immediate reach, demand and learning data. SEO builds structural organic visibility. GEO increases the likelihood that the organization is understood, mentioned and cited in AI answers. Budget and capacity only go to the combination that demonstrably contributes to the desired result.

You can, through Developer as a Service. You do not need to add a marketing program or broader growth engagement.

We do test which user problem, business process or growth objective the software needs to serve. We then define development capacity, ownership, technical principles, a clear roadmap and a prioritized backlog. This ensures developers do not merely build what is possible, but what actually helps the organization move forward.

Through DaaS, we develop and improve internal portals, CRM environments, project management systems, customer portals, dashboards, web applications, planning tools, quotation and order processes, API integrations, automations, AI applications and industry specific software.

Technical possibility is not the starting point. We first determine which process, user and result are central. We then decide what requires custom development, what can be integrated and what should not be built.

We can when a custom environment demonstrably fits better than an existing product or integration. We do not build custom software simply because it is technically interesting.

We investigate roles, processes, information needs, existing systems, maintenance and total cost. When custom software makes the organization simpler, faster or less dependent, it receives a place on the DaaS roadmap.

With Developer as a Service, you reserve an agreed amount of development capacity each month for your software and priorities.

Every collaboration starts with the context, technical baseline, a clear roadmap and a prioritized backlog. The team builds, tests, releases, measures and improves. New features, integrations, defects, security, usability, performance and technical debt are managed within one connected cycle.

DaaS fits the reality that software is never truly finished. The direction remains clear while priorities can move each month with usage, feedback and the organization.

Yes. Without a roadmap, DaaS becomes a collection of isolated tickets. Every collaboration therefore has a roadmap that describes the desired product, the main user problems, milestones, dependencies, technical choices and objectives for 30, 90 and 365 days.

The roadmap is not a frozen promise. We update it each month based on usage, results, feedback, risks and new priorities. The selected steps are translated into an ordered backlog for the development team.

No. SaaS means Software as a Service. That means you subscribe to an existing software product.

DaaS means Developer as a Service. That means you buy structural development capacity. The developers work on your software, processes and priorities. It is not a standard software package but an ongoing development service.

upMention deliberately does not offer software development as a fixed project. A fixed scope assumes that all needs are known in advance and will not change during development. In practice, the best insights emerge when people use the software.

Within DaaS, we do make clear agreements about capacity, budget, quality, roadmap and milestones. We only avoid the false certainty of a frozen scope. This allows the software to be adjusted each month without starting a new quotation or handover for every improvement.

We can through DaaS when the existing software can be taken over responsibly from a technical and organizational perspective. We start with a focused onboarding and assessment of the code, architecture, security, integrations, infrastructure, documentation, users and outstanding risks.

We then make clear what can remain, what needs to be repaired first and which development creates the most value. This is translated into the roadmap and backlog. A complete rebuild is only considered when there is a supported technical and business reason.

We can through DaaS. We do not start with a long list of features, but with the user problem, process and value the software needs to create.

We then define the first usable version and place it on a clear roadmap. We release in steps, monitor usage and continue development based on evidence rather than assumptions. This allows a first version to grow into software that continues to fit the organization.

The roadmap determines the direction. The backlog contains the concrete work. For each item, we define which problem it solves, for which user, which value is expected, which dependencies exist and how we will determine whether it works.

During fixed review moments, we determine the order together. Value, risk, urgency, technical necessity and required capacity are weighed against each other. Isolated ideas do not automatically take priority over work that demonstrably contributes more to the desired result.

Yes. We can work independently, provide extra capacity or take over a specific part of the technical work.

Upfront we agree who is responsible for architecture, code review, testing, releases, infrastructure and technical decisions. We plug into existing development processes when they work well.

Existing code, data, brands and other property of the organisation remain the organisation's.

For newly developed code, designs, general components and third-party technology used, we record ownership and usage rights upfront. These agreements are explicitly captured in the proposal and contract.

This can be organized within DaaS when it creates the best division of responsibilities. Maintenance, updates, monitoring, defects, performance and security are part of the ongoing roadmap and backlog.

For hosting, backups, incidents, access, security updates and external suppliers, we define precisely who is responsible for what. We do not accept responsibility that has not been explicitly agreed and organized.

Yes. Development capacity can be adjusted each month based on the roadmap, backlog, desired speed and available capacity.

We plan changes carefully so that knowledge, quality and continuity are preserved. Less capacity requires sharper choices. More capacity only makes sense when the roadmap, decision making and preparation are sufficiently workable.

We manage code centrally and work with version control, code review, documentation, testing and clear agreements about architecture, infrastructure, integrations and releases.

The roadmap and backlog record not only what is being built, but why decisions were made. The collaboration should not depend on one developer or one person at the client. We therefore build knowledge deliberately across the team and make transfer part of normal work.

We have preferences and experience, but we don't automatically choose the same technology for every assignment.

The choice depends on the existing environment, desired features, security, scalability, available knowledge and future maintenance. For existing software we try to avoid unnecessary technical replacement.

Hidden growth potential is not only an opportunity that nobody has seen yet. It can also be locked inside a delayed decision, knowledge that is not connected, a customer need that is not translated, or a recurring pattern in leadership, collaboration or processes.

We investigate where new value can be created and what currently prevents that value from being realized. The outcome may be a market move, stronger proposition, better visibility, different way of working, simpler process or software solution.

upMention Intelligence is the environment and way of working we use to bring together information from the organization, customers, market, results, processes, systems and digital channels. Every source, observation and assumption remains identifiable, making it clear what a conclusion is based on.

The environment helps identify patterns, contradictions, missing information and possible growth opportunities. AI supports collection, organization, comparison and analysis. Our strategists assess what the information means, which hypothesis still needs to be tested and which choice is responsible.

The selected direction is connected within the same environment to a roadmap, backlog, ownership, execution and results. This keeps visible why something received priority and what it delivers in practice.

We start with a concrete research question. We then bring together existing information from leadership, employees, customers, CRM, Analytics, sales, finance, processes, systems, search behavior, advertising, competitors, reviews, social media, AI answers and public sources.

Within upMention Intelligence, we distinguish facts, observations, interpretations and assumptions. We look for patterns and contradictions between what the organization wants, what it does, what customers experience and what the results show.

Only when information is missing do we conduct focused additional research. This can include interviews, customer research, market research, technical analysis or, when the question calls for it, an organizational constellation.

Compensatory marketing occurs when additional campaigns, content, visibility or media budget are used to compensate for a problem that sits somewhere else in the organization.

Marketing may work harder while the strategy is unclear, the offer is unconvincing, sales does not follow up, service fails to meet expectations or responsibilities are confused. This creates more activity but does not solve the cause.

We therefore first test whether marketing is truly the right point of leverage. When the constraint sits elsewhere, we make it discussable and direct the first action there. Marketing works best when it strengthens what is aligned on the inside.

They can when the question is not only about figures, market or processes, but also about relationships, roles, leadership, loyalties, exclusion or recurring patterns within the organization.

An organizational constellation is then an additional form of research. It can make visible which relationship or order may be influencing the situation and which question is not yet being asked. The constellation is not evidence and does not replace data, conversations or business analysis.

We record observations and hypotheses from the constellation in upMention Intelligence and test them against other sources. We only use this method when it serves the question and the people involved consciously agree to it.

You do not receive an isolated report, but a supported choice and a working management rhythm. Within upMention Intelligence, sources, insights, assumptions, opportunities, decisions and results remain connected.

The selected direction is translated into a roadmap for 30, 90 and 365 days, a prioritized backlog, ownership, budget, capacity and measurement points. Work that we execute enters the same cycle of doing, measuring, learning and adjusting.

We can advise and execute, but we do not automatically deploy every discipline. The analysis determines which execution is needed and which responsibility sits most efficiently with upMention, the organization or an existing partner.

That may be SEO, GEO, online advertising or DaaS on its own. It may also be a combination. And when the first step does not sit in marketing or technology, we say so. The desired result takes priority over the size of our engagement.

We record the baseline, desired change and main assumptions in upMention Intelligence. We then connect the work to early signals, commercial results and effects within the organization.

Each month, we discuss what was executed, what was learned, which assumptions were confirmed or rejected and what this means for the roadmap, backlog, budget and capacity. We do not defend an old plan when reality shows something different.

For us, entrepreneurship is the ability to choose a direction, carry responsibility and give an appropriate response under uncertain circumstances. It involves seeing opportunities, organizing people and resources, making decisions and learning from their effect.

It also means knowing what you can influence, what you need to accept and what you need to stop or release. Growth is not always about doing more. Sometimes the entrepreneurial choice is to simplify, set a boundary or create space for others.

In an organization that is strongly led by an owner or founder, the entrepreneur influences the whole every day. What that person values, rewards, avoids, solves personally or postpones becomes part of the pace, culture and decision making.

This is often the exact strength that created the organization. In a later phase, the same strength can limit growth. We only investigate this when the business question provides a reason. We do not make every problem personal and we do not look for an entrepreneur to blame.

We do not decide this in advance. We compare information from the market, customers, finance, processes, systems, teams, leadership and results. We then investigate at which level the pattern repeats and where a change would genuinely have an effect.

Declining demand may come from the market. Slow growth may also relate to an unclear proposition, insufficient capacity or decision making that remains with one person. Several levels often interact. We therefore record the first explanation as a hypothesis and test it before intervening.

No. This remains organizational advice with room for reflection on entrepreneurship and leadership. We focus on the business role, concrete choices, behavior within the organization and the consequences for collaboration, execution and results.

We do not diagnose or treat personal issues. When a question requires personal therapeutic support, that sits outside the engagement and belongs with an appropriate specialist. We also only use an organizational constellation within a clear business question and with conscious consent.

The entrepreneur's fingerprint is what their daily presence makes possible and difficult within the organization. Often without consciously intending to, the entrepreneur sets the rhythm for quality, speed, conflict, risk, customer focus, making mistakes and taking responsibility.

We compare the intended culture with what employees, customers, processes and results actually show. This reveals where the entrepreneur's example strengthens the organization and where an unintended message reduces its room to move.

A founder's experiences can develop into strong business principles. Examples include always persevering, solving everything personally, disappointing nobody, remaining independent, guarding quality or acting on opportunities immediately. For years, these principles may be exactly what the organization needs.

When the same movement keeps repeating while the context changes, it can become a constraint. We never use personal history as an automatic explanation. We only investigate it when a recurring business pattern cannot be sufficiently explained by market, knowledge, structure or capacity.

We only record relevant business observations and hypotheses. Personal details that are not needed for the engagement do not belong in upMention Intelligence.

This happens regularly. Decisiveness can turn into impatience. Quality control can become micromanagement. Loyalty can make stopping impossible. Service can lead to overpromising. Independence can block asking for help or delegating.

The answer is not to remove the strength. We investigate which form of it still serves the current phase and which opposite quality is now needed. Speed may need structure. High quality may grow by creating clear standards and placing responsibility deeper in the organization.

Signals include decisions, exceptions and escalations repeatedly ending up with the same person, delegated tasks returning, employees being spared and the entrepreneur constantly filling gaps. The organization may appear independent, while in practice it waits for one person.

We first investigate whether there are genuinely enough people, knowledge, authority and systems. Overresponsibility is not automatically a personal pattern. Sometimes the organization is in fact understaffed or poorly designed.

When the entrepreneur structurally carries more than belongs to their role, we return tasks, decision rights and ownership to the appropriate place. This requires clear expectations, support and a willingness to let others carry their own responsibility.

Standing in your own place means carrying final responsibility for direction and continuity without taking over everyone's work. You do not need to sit above every detail, but you do need to be clear about purpose, boundaries, decisions and consequences.

We distinguish the vertical responsibility of owner, leadership or management from horizontal collaboration between colleagues and partners. We then define what belongs to the entrepreneur, what belongs to management, what belongs to teams and where upMention or another partner carries responsibility.

Good delegation is not pushing a task away. It requires a clear context, desired result, authority, available resources and a moment for feedback. Without those conditions, autonomy does not emerge. Uncertainty or reverse delegation does.

Healthy autonomy also means being able to ask for help, accept expertise and organize dependencies. The goal is not an organization without dependencies. The goal is an organization that is not trapped by one person, supplier or system and where it is clear who is accountable for what.

A new step makes an entrepreneur visible. Doubt, shame and fear of failure or even success may arise. This does not automatically mean the direction is wrong. It may also be the tension that belongs to growth, leaving the familiar behind and making a real choice.

In practice, this can appear as endless preparation, underpricing, overpromising, hiding behind the work, constantly starting a new plan or continuing to postpone a decision. We do not attach a label to this. We make the pattern concrete and distinguish useful doubt from repetition that blocks movement.

Small tests, honest feedback and clear decision moments make it possible to learn without exposing the whole organization to one large gamble.

The origin is what the organization grew from. This may be the founders' original experience, intention, frustration, craft or value. The purpose is what the organization wants to keep contributing, for whom and why it matters.

Products, people, channels and technology can change. The deepest contribution of an organization usually changes less quickly. When contact with it is lost, fragmentation, loss of focus and sometimes compensatory marketing can arise.

We map the line between origin and purpose through the founding story, core values, customers, proof, results and the current proposition. We then test which form still fits the present time.

They can. An entrepreneur may still be pioneering while the organization mainly needs structure, repeatability and transfer. The opposite also occurs: the organization needs renewal while the entrepreneur mainly wants to preserve, harvest or step back.

Such a difference can create unrest, slow decisions, micromanagement, loss of initiative or uncertainty about succession. This is not automatically a personal failure. It may mean that the entrepreneur and organization are facing a transition that has not yet been consciously shaped.

We look at the organization's history, growth, crises, leadership changes, team, systems, customers and results. We then determine what should be preserved, what needs a new form and which role fits the next phase.

Acceleration fits when direction, evidence, ownership and capacity are sufficiently clear. Pace then helps capture opportunities, learn faster and build results.

Slowing down is needed when important assumptions conflict, roles are unclear, the organization is overloaded, a rupture or transition is still affecting the present or all decisions continue to depend on one person. In that situation, executing harder usually increases the confusion.

Slowing down does not mean doing nothing. It means observing more accurately, ordering choices, setting boundaries and deciding what stops. The organization can then regain speed with less waste.

Every insight must lead to a test, decision or action. This may concern roles, decision rights, meeting structure, hiring or developing people, stopping an activity, proposition, pricing, sales, service, marketing or the software roadmap.

Within upMention Intelligence, we connect the observation to a hypothesis, supporting evidence, owner, action and measurement point. This makes it visible whether the change genuinely has an effect and prevents a personal or systemic insight from disappearing into a drawer as an interesting conversation.

We can when the transition affects direction, customers, people, knowledge, systems or continuity. We map what should be preserved from the original intention, which knowledge and relationships need to be transferred and which role the departing and incoming leader will hold.

A good transition requires more than tasks and documents. Decision rights, trust, communication and a careful ending of the previous phase also need to be right. What is not completed often continues to affect the new phase unnecessarily.

We translate the transition into a roadmap for 30, 90 and 365 days. Legal, tax or personal support outside our expertise is organized with appropriate specialists.

Every collaboration with upMention starts from €2,500 per month, excluding VAT. The exact investment depends on the expertise, capacity, amount of execution and technical responsibility required.

Media budgets, licenses, hosting and other external costs are not automatically included. The proposal states which capacity and work are included each month, which results are central and which costs fall outside the collaboration.

Every collaboration can be adjusted and ended month by month. We do not use long mandatory terms to hold a client in place.

At the same time, we look beyond one month. We work with a direction for 30, 90 and 365 days so that choices can build on each other and results can be assessed fairly. Each month, we decide together what continues, what changes and which capacity is needed.

We want clients to choose upMention again each month because the collaboration delivers relevant work and demonstrable value. Not because a long contract makes leaving unnecessarily difficult.

That is why every collaboration can be adjusted or ended month by month. This freedom also requires discipline from us. Each month, it must be clear what we are doing, why it has priority, what it delivers and why another month makes sense.

We need subject knowledge, access to relevant information and timely decisions. How much time that takes depends on the assignment.

For online advertising, regular feedback on request quality, sales opportunities and revenue is especially important. For DaaS, a fixed point of contact is needed for priorities, feedback and decisions on the roadmap and backlog. For a broader growth engagement we periodically need time for conversations, decisions and the monthly decision moment.

Every collaboration has at least one fixed monthly decision moment. We discuss results, completed work, new information, constraints, assumptions, roadmap, backlog, budget and capacity.

DaaS, active campaigns or urgent phases may require shorter operational meetings. These do not replace the monthly decision moment. The monthly meeting is where we jointly choose what will create the greatest difference in the next period.

We only use information that is needed for the agreed work. Access is restricted to the people and systems involved.

Upfront we record which data is processed, where responsibilities sit and which external services are used. For online advertising this can also involve ad platforms, audiences, cookies, consent, conversion measurement and integrations with Analytics or CRM. When a data processing agreement is needed, we include it in the partnership.

We use AI to organize large amounts of information, compare sources, identify patterns, support analysis, accelerate content processes and develop software features. upMention Intelligence helps us keep sources, observations, assumptions and conclusions distinct.

AI does not take over commercial or organizational decisions. Our people assess source quality, verify important facts, weigh context and risks and remain responsible for advice, publication and execution.

For confidential information, we define which systems are used, which data may be processed and which human review is required.

We then adjust the choice, roadmap or backlog. We investigate why the assumption was incorrect, which new information is available and what this means for the result, budget, capacity and planning.

A rejected assumption is useful information. The goal is not to defend an earlier plan, but to determine with increasing accuracy what genuinely helps the organization move forward.