How do we grow through an open-source ecosystem?

Grow through an open-source ecosystem by opening a useful, extensible core that others can confidently build on, then charging for additional operational or organisational value. Define each participant's benefit, publish stable rights and contribution rules, and measure the path from successful use to retained paying accounts. Reinvest in the shared project.

Grow through an open-source ecosystem by making a useful core available under clear rights, giving other organisations a reason to extend and support it, and selling additional value that those users genuinely need. For a post-seed software startup, start with one developer problem, one maintained integration and one credible commercial offer. The strategic test is reciprocal: users, contributors and partners should gain more by building with the project than by working around it. Your company needs a sustainable return too.

The recommendations below form a proposed operating method. The running example is a hypothetical data-validation engine, not a customer case or a measured result. Its open engine checks incoming records; independent builders add connectors; the company considers managed operation and organisational controls as paid additions.

How does an open-source ecosystem actually create growth?

An open-source ecosystem creates a possible growth mechanism through shared adoption, complementary products and reinvestment. The company benefits when the shared project makes its own commercial offer more useful or easier to trust. Each transition needs evidence: accessible code does not automatically produce users, users do not automatically contribute, and contributions do not automatically create buyers.

Separate four activities. Using open source incorporates someone else’s software. Contributing upstream improves an existing project. Stewarding a project accepts responsibility for its direction and maintenance. Commercialising an ecosystem sells an outcome around that shared foundation. You can pursue the first two without launching another project. Consider that route before taking on stewardship.

The Linux Foundation’s commercial ecosystem guide connects useful projects, commercial products and resources reinvested in the community. Treat that practitioner framework as a hypothesis to operate, not an automatic cycle. For the example engine, a connector might remove an adoption obstacle. Continued use might then expose a need for managed scheduling. The connector author might earn implementation work. Check each link separately.

Research supports a narrower conclusion than the familiar claim that public activity causes growth. Wright, Nagle and Greenstein’s August 2024 working paper matches GitHub accounts to venture-backed software firms identified in PitchBook. The authors find positive relationships with financing, valuation and exits, but attribute at least two thirds of the initial relationship to selection. Their mechanism analysis favours shaping code, signalling and engaging potential clients over general learning or production savings.

Likewise, Hoffmann, Nagle and Zhou’s 2024 value study models replacement costs using software-use datasets, code volume and labour assumptions. Its economy-wide value estimate is neither a revenue market nor a valuation for your project. Shared usefulness and the part your company can earn are different quantities.

Example growth hypothesis: “Teams validating incoming records can adopt the engine independently. Connector maintainers can reach relevant users. Organisations that need accountable operation can choose our managed service.” Interview each group before assuming the exchange works. If the adopting teams differ from your intended buyers, revisit how to define an early-stage startup’s ideal customer profile.

Would another company still have a good reason to build on your project if it never bought from you?

Three people attach red, yellow and olive extensions to a shared blue structure in an open workshop

What should we open, and what counts as open source?

Open the smallest coherent component that solves a recurring problem independently and creates a useful connection to your business. Then describe its rights accurately. The Open Source Initiative’s definition requires more than visible code: it includes modification, redistribution and use without discrimination against fields of endeavour, including business use.

Use the following decision table as a proposed scope assessment:

Possible open componentIndependent usefulness to establishResponsibility you accept
Library or engineDevelopers complete a real task inside their own applicationCompatibility, releases and integration guidance
Client or connectorUsers can reach a supported service or move usable dataAuthentication guidance, version support and failure handling
Protocol implementationIndependent implementations can interoperateSpecification, conformance criteria and change process
Entire applicationA team can operate a complete, useful productDeployment guidance, upgrades and broader support
Contribution to an existing projectAn accepted improvement serves shared usersUpstream review and that project’s governance

Example scope: open the validation engine, its rule format and an independently runnable example. Keep a proposed hosted operations console separate and labelled. A connector that works only after an unexplained sales approval does not establish the same independent value. State any service dependencies before installation.

Keep three boundaries visible: the licence for the code, the terms for a hosted service, and permission to use the name or logo. Do not describe the whole company as open source when only a client library is open. Public development, open governance and open licensing are separate properties; state which applies to each component.

The OSI-approved licence directory provides a starting point for recognised licences. Compare permissive and copyleft approaches with the intended integration and distribution in view. Copyleft can be open source; a restriction against a category of commercial use is a different issue. Avoid confusing the Business Source License with the Boost Software License merely because both may be abbreviated BSL.

GitHub’s legal guide distinguishes a public repository from a licensed project and explains why dependencies and contributor rights matter. Before release, review ownership, compatible dependency terms and material that should remain private. A source-available model may fit your strategy, but use that description openly when its restrictions depart from open-source rights. Calling restricted code open source obscures the choice a future partner must make.

What should users, contributors, partners and our company each gain?

An ecosystem participation agreement should give each group a concrete benefit and a manageable obligation. Shared enthusiasm is insufficient when one participant receives the commercial opportunity while another inherits the maintenance. Write down the exchange before recruiting people into it.

For the hypothetical engine, use this example participation map:

ParticipantReason to participateProposed contributionReason to reconsider
UserSolve validation problems with control over deploymentReproducible feedback when willingSetup or support requires disproportionate effort
ContributorImprove a tool they depend on; gain recognised responsibilityA bounded correction, example or design proposalReviews stall or decisions are unexplained
Integrator or resellerDeliver specialist work to relevant usersMaintain a connector and document its limitsThe vendor copies the offer and blocks distribution
Cloud providerOffer useful workloads to its customersEngineering, distribution or other agreed supportResponsibilities and commercial rights remain unclear
Your companySell additional outcomes and learn from adoptionCore maintenance, reliable interfaces and public decisionsSupport absorbs the capacity needed to deliver

Do not require every user to become a contributor. Let someone provide a reproducible issue, translation, migration note or helpful answer without becoming a developer. For a first external integration, ask one willing builder to complete a real task alongside a maintainer. Record where the work becomes dependent on undocumented knowledge.

Recruit in the communities where that task already matters. Offer a useful example or accepted upstream improvement before asking people to move into another discussion space. Keep decisions and resolved answers publicly accessible where appropriate. For the mechanics of reciprocal delivery, use turning product integrations into shared growth.

Agree who owns installation support, version compatibility and escalations. A reseller relationship also needs clear responsibility for customer communication and service delivery. In the example, the connector author can support mapping errors while the engine maintainer investigates a confirmed core defect. Tell users where the boundary lies.

Who gains the least from your proposed ecosystem, and what would make participation worthwhile for them?

How can we monetise open source without undermining adoption?

Monetise an open-source project by charging for an additional outcome whose value survives comparison with self-service use and alternative providers. Keep the open product useful on its stated terms. Publish the commercial boundary early so contributors can decide whether their work supports a bargain they accept.

The following comparison is a proposed decision aid, not a ranking:

ModelBuyer receivesMain operating trade-off
Managed or hosted serviceSomeone operates the software and handles agreed operational workInfrastructure, reliability and support become your responsibility
Open coreDefined proprietary capabilities alongside an open productThe boundary needs careful documentation and maintenance
Support subscriptionAccess to expertise under an agreed scopeExpert availability must remain sustainable
Implementation or trainingHelp reaching a working deployment or building internal capabilityDelivery capacity constrains growth
Dual licensingAlternative licence terms for the same codeYou need rights sufficient to offer both sets of terms

Example commercial boundary: the engine runs meaningful validations without payment. The company proposes managed execution, retained audit history and centrally administered policies as additional services or proprietary capabilities. Publish where each belongs. If basic installation or ordinary collaboration is deliberately obstructed to force purchase, revise the boundary rather than dressing the obstacle as enterprise value.

The State of Commercial Open Source 2026, from Linux Foundation Research and Serena, reports that companies combine revenue models and that organisational capabilities are common open-core boundaries. It surveyed 225 qualified founders and decision makers through a partner-distributed web survey fielded from March to June 2026. These are self-reported practices from a selected population, not proof that copying a particular model improves your results.

Start with one buying reason you can deliver well. A hosted service plus implementation can be coherent when onboarding leads to repeatable operation. An expanding catalogue of bespoke services may instead consume the maintainers’ attention. Keep project maintenance, customer delivery, hosting and acquisition effort visible separately. Judge sustainability after including that work.

Separate the developer’s reason to adopt from the organisation’s reason to purchase. In the example, the developer can demonstrate correct validations; an operations owner must assess recovery and upgrades; security and procurement need suitable evidence and terms; the accountable buyer must authorise the purchase. Prepare a short evaluation record connecting each requirement to a responsible person and an answer. Offer an explicit route from the documentation to that conversation. A request for single sign-on may reveal an organisational need, but it still needs qualification and a buying decision.

The commercial model should reflect both target customers and company stage. In Linux Foundation Research and Serena’s survey, enterprise-focused vendors gate security features almost three times as often as SMB-focused vendors: 41% versus 15%. The executive summary identifies the CTO or VP Engineering as approving purchases in 46% of cases. Managed cloud adoption rises from 35% among early-stage companies to 66% among later-stage companies. Use these distinctions to evaluate which organisational capabilities your target buyers need and whether your team can sustain managed operation at its current stage.

The open release should be work you are prepared to stand behind even when a user never pays. Charge openly for what you add. In the example, a self-hosting team may be a satisfied long-term participant while a different organisation buys managed operation. Neither needs to be treated as a failed version of the other.

Could a developer explain your open and paid boundary accurately after reading one page?

Which governance and licensing decisions preserve long-term trust?

Trustworthy governance makes decision rights, contribution terms and future change procedures inspectable. A commercial steward can lead a project honestly. Problems arise when public participation suggests influence or durable rights that the actual rules do not provide. Publish the limits of participation alongside the invitation.

Use this example governance record before soliciting substantial contributions:

DecisionWhat to publish
RoadmapWho proposes, accepts and rejects work; how reasons are recorded
Maintainer authorityHow responsibility is earned, reviewed and transferred
Code and contribution rightsOutbound licence, inbound terms and ownership requirements
Project identityWho controls trademarks, domains and release credentials
ContinuitySubstitute maintainers, supported versions and security reporting route
Material changesConsultation process, version scope and migration information

A Developer Certificate of Origin and a Contributor License Agreement are different instruments. The DCO 1.1 text asks contributors to certify their right to submit under the indicated licence. A CLA’s rights depend on its wording. As GitHub’s legal guidance explains, offering proprietary alternatives to copyleft contributions may require additional rights from contributors. Have the proposed arrangement reviewed before promising dual licensing; a sign-off alone does not settle that question.

Consider a foundation when several competing companies want to contribute but need neutral ownership of the shared project. Before choosing this route, be prepared to transfer the project trademark and give up unilateral control over the roadmap; budget for membership and administrative overhead. Inspect the charter, voting rights and maintainer appointment process. Foundation membership alone does not answer who can decide. Dawn Foster’s November 2024 three-case study finds greater organisational diversity in the OpenSearch, Valkey and OpenTofu forks, especially under neutral foundation stewardship.

Licence changes deserve the same scrutiny as product changes because they affect what partners can safely build next. The histories differ:

Documented changeWhat followed or changed againLesson for evaluating your own decision
Elastic changed licensing in 2021OpenSearch forked the last Apache 2.0 code; Elastic added AGPLv3 for relevant source portions in 2024Distinguish source components, distributions, versions and later choices
Terraform’s BSL change prompted the OpenTofu fork announcement in 2023Independent builders organised an alternative around continuing open developmentInclude partner investment in the consequences of changing future rights
Redis changed terms in 2024 and added AGPLv3 from Redis 8 in 2025Valkey continued from the open code; Redis acknowledged damage to its community relationshipExamine trust and governance alongside the intended commercial protection

These histories do not establish that every user left or that any particular revenue result followed. Nor does changing future releases answer the obligations attached to already released code. Review exact terms and copyright rights; communicate version boundaries rather than announcing that everything has changed or nothing has changed.

The implicit promise matters alongside the licence. A contributor may have worked within perfectly clear legal terms while expecting a stable, useful shared project. If your commercial model now requires disappointing that expectation, discuss the real tension. Consultation cannot remove the trade-off, but it gives others information they need before investing further.

Read also: building a community around your product’s purpose.

How do documentation and contribution design turn interest into useful adoption?

Developer adoption needs a complete route from discovery to a successful task, then a credible route into production. Documentation, runnable examples and public answers should carry enough context for someone to succeed without the original author present. Treat that independence as an acceptance criterion for the project.

The Center for Open Science’s May 2025 OSF account describes onboarding webinars, starter tasks, public governance, API documentation, office hours and community-led funding. It gathers integration requests through support and community conversations.

Example adoption exercise: ask a developer unfamiliar with the validation engine to install a specified version, run the supplied sample, introduce an invalid record and interpret the failure. Observe the point where they need help. Then ask them to integrate a real input and recover from an interrupted run. Record first successful use separately from readiness for production; a fast demonstration is only the first milestone.

Publish prerequisites, supported versions, expected output, common errors, upgrade guidance and a clear route for unresolved issues. Show one complete integration before cataloguing every option. Include limitations and the paid boundary in the same documentation path. Do not impose a universal installation-time target; compare the time and assistance required for the task your audience actually needs.

Make each example preserve the reasoning needed to adapt it: why the rule exists, what inputs it assumes and what failure looks like. A public answer can then help the next developer or their assistant without repeating the private conversation. Apply turning customer questions into valuable public knowledge to recurring adoption obstacles.

For contributions, publish a bounded issue with expected behaviour, relevant code, reproduction steps and a named reviewer. Agree a response target you can maintain, distinguish initial acknowledgement from a substantive review, and explain rejected work. Offer documentation and issue-triage paths too. Measure returning contributors and accepted improvements against review effort, rather than maximising submitted changes.

Before encouraging production dependencies, assign a security contact, a private reporting route and responsibility for preparing and communicating fixes. State which versions you maintain and how users learn about upgrades. Track whether release access, specialist knowledge or review authority rests with one person. Arrange a substitute and exercise the handover. More submitted changes should not conceal a growing queue that only one maintainer can resolve.

Use automation for reproducible environments, routine checks, duplicate detection and proposed documentation updates. For AI-assisted submissions, require a responsible author who understands the change, can explain its origin and supplies reproducible evidence. Keep acceptance with maintainers. If automated submissions increase review time or produce unverifiable reports, constrain intake. Fewer repetitive tasks should create more attention for judgement, not an obligation to process unlimited generated work.

Could a capable newcomer use and improve your project without needing access to an unwritten explanation?

How should we work with cloud providers and commercial alternatives?

A cloud partnership is useful when distribution and easier operation outweigh the dependency it creates. Evaluate who controls discovery, the customer relationship, service quality and the work of maintaining compatibility. An open-source licence is not a complete commercial defence, and restricting future code does not remove the possibility of competing implementations.

The distinction matters in the MongoDB history. MongoDB’s SSPL FAQ dates its Community Server change to October 2018 and describes obligations for providers offering the software as a service; it also states that SSPL is not OSI-approved. AWS’s Amazon DocumentDB FAQ says its service does not use MongoDB SSPL code and interacts with the Apache 2.0 MongoDB APIs; its compatibility documentation lists the supported API versions. Do not describe that service as a fork of MongoDB code or assume API compatibility means identical behaviour.

Example partnership decision: compare operating the validation engine yourself, allowing an integrator to offer it, and distributing a managed service through a cloud marketplace. For each route, record who receives support requests, what customer information is available under agreed permissions, how upgrades reach users, what your company contributes and how either party can leave. Request an accountable counterpart before announcing a partnership.

Build differentiation that users can inspect: reliable operation, specialist knowledge, responsive support or useful organisational capabilities. Do not rely on an expectation that competitors will decline rights your licence grants. Also avoid treating every cloud provider as an adversary; the participation map should show what a worthwhile cooperation would require.

For a reader choosing infrastructure today, OpenSearch, Valkey and OpenTofu provide official starting points for examining open alternatives in their respective categories. They are not interchangeable replacements for your product. Compare present functionality, migration, maintenance and support for the actual workload. A simpler proprietary service or an upstream contribution may fit better than founding another ecosystem.

How do we measure open-source adoption through to revenue?

Measure open-source growth through account cohorts with explicit events, observation windows and known coverage gaps. Keep project health separate from commercial performance. Stars, downloads and commits measure particular activities; they do not identify recurring production value, purchase authority or retained contracts.

Use this proposed measurement map, adapting the events to your product:

StageExample observable eventDenominator and interpretation
DiscoveryDocumentation visit or repository interestReach within the observed channel, not unique adopting companies
ActivationFirst successful validation on a meaningful inputEligible new deployments observed during the chosen period
Continued adoptionRepeated useful work across the relevant operating cycleActivated deployments old enough to be assessed
Commercial intentExplicit request for managed operation, procurement or agreed supportIdentified eligible accounts, separated by segment
PurchaseA paid contract startsMature activated or qualified account cohorts, stated separately
Retention and expansionRenewal, continued workloads or additional purchased scopeAccounts eligible for each event
Project healthUseful contributions return; releases and reviews remain sustainableContributors, issues and maintainer capacity, each with its own definition

Example cohort record: group organisations first activated in the same month, separate self-hosted and hosted deployments, and preserve their initial segment. At the agreed review date, show which reached repeated use, requested commercial help and bought. Report observed counts and elapsed time. Exclude internal trials and automated installations from the chosen adoption event; explain exclusions rather than treating every download as a new organisation.

Do not put a recent cohort beside a mature cohort and interpret the lower purchase rate as deterioration. Where no contract has yet occurred, retain the account as unresolved at the observation cutoff. State your identity-matching rules, consented telemetry scope and unknown self-hosted population. Do not convert a public contributor profile into an assumed sales account. Offer a useful way to self-identify when someone wants commercial help.

The November 2026 Linux Foundation and Serena survey reports that 38% do not measure unpaid-to-paid conversion and 42% do not measure time to first contract. Its finding that 77% convert within a year describes reporting companies among those tracking the metric. It does not mean 77% of open-source users purchase. Use the report to ask better measurement questions, not to set a universal conversion target.

Keep first attribution, ecosystem assistance and the purchasing route as separate fields. A partner can influence a purchase without sourcing it. Track retained recurring revenue, expansion and gross margin by deployment and segment; compare acquisition payback only with an explicit allocation of sales, community and developer-relations effort. Include hosting, delivery and support in the profitability view. Useful users and sustainable paying accounts both matter, but they answer different questions.

For causal claims, compare equivalent eligible groups and timing, using a controlled rollout where appropriate. Otherwise report an association and competing explanations. Follow the same discipline when deciding what to measure in early go-to-market tests.

Which transition in your ecosystem currently depends on an assumption rather than an observed event?

What should we do first, and when is this the wrong approach?

Start with a bounded adoption and commercialisation experiment whose maintenance fits your team. Defer an ecosystem launch when you lack a recurring shared problem, rights to release the code, capacity to support it or a credible paid outcome. Publishing software cannot repair a proposition that nobody needs.

Use this example sequence as a decision process, not a promised timetable:

  1. Establish the problem. Observe intended users doing the task. Compare existing open and proprietary options. Continue only when your contribution has a useful, specific role.
  2. Publish the bargain. Agree the open scope, commercial offer, licence, governance and continuing maintenance owner. Identify the users who should remain satisfied without buying.
  3. Observe independent success. Have an unfamiliar user complete the task and an external builder attempt one extension. Repair missing context before promotion.
  4. Offer the paid outcome. Ask eligible organisations about operation, support and purchasing requirements. Treat requests for help as evidence to investigate, not as contracts already earned.
  5. Review both systems. Compare recurring user value and commercial progress with maintainer effort. Continue, narrow the scope, contribute upstream or stop recruiting new dependencies when the responsibilities are unsustainable.

Publish roadmap decisions with their evidence and status. Invite input without making every request a commitment; explain how priorities change. For the communication around those choices, see making a roadmap useful and exciting to future customers.

Choose a different route if your differentiation depends on keeping the proposed core private, your buyers prefer a complete service with no developer adoption, or an established project already solves the shared problem well. Integrating with that project may serve customers with less duplicated work. If your team cannot maintain existing commitments, reduce scope and communicate a supported transition before seeking more attention.

How can Poldermarketing help connect the ecosystem to go-to-market?

Piet Baudoin of Poldermarketing helps post-seed startups connect technical adoption to a clear commercial offer and a practical go-to-market process. For an open-source product, that can mean clarifying the open and paid boundary, improving discovery in Google and AI answers, and preserving useful context from an opt-in enquiry through follow-up.

Piet works remotely in Dutch and English. Alongside positioning and findability, he builds and runs AI automations with care: lead follow-up, enrichment and qualification, CRM setup, reporting, content distribution and tool integrations. Read how Piet builds and runs the work, or request a no-cost growth scan. A concrete starting point is one adoption path whose next commercial step is unclear, with technical and licensing decisions retained by the responsible specialists.

How this connects to my larger vision

I think most useful foundations should be open, so that people can understand them, improve them and build something their original maker could not have imagined. An open-source ecosystem makes that idea practical. One team creates a reliable core, another sees an application in its own field, and someone elsewhere removes a limitation that both had accepted. I want technology to make that kind of cooperation easier across the world, with fewer people having to ask permission before they can contribute something worthwhile.

For me, sharing the core also means accepting that other people have purposes of their own. They may never become customers. Their work can still make the shared foundation more capable. A company can earn its place by maintaining that foundation carefully and offering additional help that people freely choose. That gives commercial success a useful direction: more resources to improve something that remains valuable beyond the company itself.

I see open architecture as a way for knowledge to travel with less friction and for people and machines to become more capable together. A clear example, an understandable interface and a dependable contribution process are small parts of that future. I want to build businesses in which those details carry the same intention as the larger ambition: leave others with more understanding, more freedom and more room to create.

Questions people ask

Can we grow through open source without opening our entire product?

Yes. Consider contributing to an existing project or opening a useful library, connector, client or protocol implementation. Define the independent task it solves and its relationship to your commercial product. Avoid publishing an unusable fragment whose only purpose is to send people to sales. Maintain the component as a product in its own right.

Is source-available software the same as open source?

No. Visible code alone does not establish open-source rights. The Open Source Initiative's definition requires permissions including modification, redistribution and use across fields of endeavour. Source-available licences may impose additional commercial restrictions. State the actual licence, version and component rather than describing the whole offering as open source because one repository is public.

Which open-source business model should a startup choose?

Choose around the additional outcome a buyer wants. Managed hosting addresses operating responsibility; support addresses access to expertise; open core adds clearly defined proprietary capabilities. Dual licensing offers alternative terms for the same code when the company holds the necessary rights. Start with one credible buying reason, then add models only when delivery capacity supports them.

How many contributors do we need before enterprise sales?

There is no universal contributor threshold. Assess whether the intended deployment is maintainable, security questions have accountable owners and the organisation has a reason to buy. A small, responsive maintainer group and reliable releases may be more useful than many occasional contributors. Measure contributor return and review burden alongside production adoption and commercial demand.

Should every open-source user become a sales lead?

No. Keep public support useful for people who never buy. Offer a commercial conversation when an organisation expresses a relevant need, such as managed operation, procurement or a defined support arrangement. Separate community participation from marketing permission. Anonymous self-hosted use will remain partly unobserved; disclose that measurement gap rather than manufacturing account identities.

Related questions

Sources

  1. Open Source Initiative (February 2024): The Open Source Definition
  2. Open Source Initiative: OSI Approved Licenses, accessed November 2026
  3. Linux Foundation: Creating an Open Source Commercial Ecosystem, accessed November 2026
  4. Center for Open Science (May 2025): Lessons from Growing the OSF Open Source Community
  5. Wright, Nagle and Greenstein, HBS Working Paper 24-040 (August 2024): Contributing to Growth?
  6. Hoffmann, Nagle and Zhou, HBS Working Paper 24-038 (2024): The Value of Open Source Software
  7. Linux Foundation Research and Serena (November 2026): The State of Commercial Open Source 2026
  8. GitHub Open Source Guides: The Legal Side of Open Source, accessed November 2026
  9. Linux Foundation and contributors (2006): Developer Certificate of Origin 1.1
  10. Elastic: FAQ on Software Licensing, 2021 and September 2024 changes, accessed November 2026
  11. OpenSearch: Frequently Asked Questions, project origins and licence, accessed November 2026
  12. OpenTofu (August 2023): OpenTofu Announces Fork of Terraform
  13. Redis (May 2025): Redis is now available under the AGPLv3 open source license
  14. Valkey: Project History, accessed November 2026
  15. MongoDB: Server Side Public License FAQ, October 2018 licence boundary, accessed November 2026
  16. AWS: Amazon DocumentDB FAQs, compatibility and SSPL, accessed November 2026
  17. Dawn Foster (November 2024): The New Dynamics of Open Source, relicensing and three fork case studies, arXiv preprint

About the author: Piet Baudoin

I am Piet. I help startups with their brand, positioning and go-to-market, and I set up AI automations that turn customer notes into draft content and follow-up tasks. I discuss the choices with you so the work helps your business and its buyers. Want to apply this to your company? Try the growth scan or book a conversation.