A launch with few sales can conceal very different problems. The right audience may never have received the offer, the presentation may have failed to explain its benefit, or buying may require changes the customer cannot yet make. A deeper problem is also possible: the issue being solved may not matter enough to justify payment and effort. Treating every weak launch as insufficient publicity leads to expensive decisions that reveal little.
Turn launch disappointment into a question you can answer
Replace a statement such as “the market did not respond” with observable behavior. For example, of 100 businesses that completed a demonstration, 20 purchased, but only 12 completed their first useful operation. This separates purchase from adoption. One business may pay out of curiosity and abandon the service; another may recognize its value but need internal authorization before starting. Their next steps should differ.
Adoption below expectations means a gap between a forecast and a defined behavior, so examine the forecast too. A target based on enthusiasm, superficial competitor comparisons, or encouraging interviews may have assigned certainty to a weak hypothesis. Missing it does not, by itself, establish poor execution. Preserve the original assumptions so the team can distinguish an unrealistic forecast from a process that failed.
The purpose of diagnosis is to guide development, validation, and market entry. The central question is not how to restore the projection at any cost. It is which adjustments could reasonably produce sustainable use and revenue, how much obtaining that answer will cost, and when continuing becomes unjustifiable. This approach leaves room for both a repairable problem and evidence that the proposal is not viable.
Define adoption through behavior that delivers customer value
Before revising campaigns, define adoption for the business. Registration, installation, and subscription are commercial or technical events; they may precede a benefit but do not establish that it occurred. For inventory software, meaningful activation might involve entering real products, recording movements, and reviewing a discrepancy that supports a correction. The event should represent useful work, rather than simply opening a screen.
Separate the first useful experience from recurring use. A shop might import its product list during a demonstration and never update its inventory again. Initial activation occurred, but an operating habit did not develop. Measure the share reaching a first result, the time required, and continued behavior over subsequent weeks. These measures reveal whether customers struggle to begin or fail to find continuing value.
The observation window must match the customer's process. A service used during monthly closing cannot be judged over the same interval as a daily customer service tool. Compare groups with similar exposure and record differences such as business size, acquisition channel, and implementation requirements. Combining new customers with established users can conceal improvement or deterioration because they have had different opportunities to use the product.
Choose one primary definition and a few supporting measures. For the inventory example, the main measure could be the proportion of paying shops recording real movements for four weeks. Supporting measures might include activation time, support requests, and cancellations. A campaign that increases contracts but attracts shops unable to operate the system would then appear as an acquisition quality problem, even while headline sales improve.
Reconstruct the assumptions behind the target
An adoption forecast combines several assumptions: how many people will be reached, how many have the problem, how many will evaluate the solution, and how many can buy and use it. Hiding these assumptions inside one target makes errors difficult to locate. Rewrite the forecast as a sequence of behaviors, identifying who is responsible for each transition and what evidence supports the expected conversion.
Consider an offer to 1,000 selected shops. The forecast assumes 200 accepted demonstrations, 100 completed evaluations, and 40 purchases. If the first three figures occur but only 20 shops buy, the observed gap lies between evaluation and contracting. This does not establish that the price is wrong. Migration concerns, trust, support expectations, or lack of purchasing authority could produce the same result.
Classify assumptions by the strength of their support. A record of money received is a fact about that transaction. A verbal intention to buy is limited evidence of interest. The conclusion that all similar shops will purchase remains a hypothesis. Maintaining these distinctions prevents five encouraging conversations from becoming a forecast that is treated as an operational commitment and used to justify fixed expenses.
Record what could contradict the explanation you prefer. If insufficient trust is the hypothesis, clearer responsibilities and support arrangements should improve progress without a price change. If they do not, that explanation becomes less convincing. Define the expected observation before seeing the result. The forecast can then serve as a revisable model of the business instead of a promise the team must defend as evidence changes.
A numerical example: 20 customers instead of 40
Imagine a business launching inventory software for small Brazilian retailers. Every figure here is hypothetical arithmetic, not a market rate or performance forecast. The monthly fee is R$ 300 per shop, variable monthly cost is R$ 60 per shop, and fixed monthly expenses total R$ 24,000. Each customer therefore contributes R$ 240 toward fixed expenses. In this simplified model, 100 customers cover those expenses.
The business starts with R$ 120,000 and spends R$ 12,000 on preparation and launch materials, leaving R$ 108,000 before the first operating month. It expects 40 active customers in month one, 80 in month two, and 120 in month three. For direct comparison, every customer counted in a month is assumed active and paying from its beginning, with no late payments, defaults, or cancellations.
Under the plan, monthly revenue would be R$ 12,000, R$ 24,000, and R$ 36,000. Variable costs would be R$ 2,400, R$ 4,800, and R$ 7,200. After those costs and R$ 24,000 in monthly fixed expenses, operating cash results would be negative R$ 14,400, negative R$ 4,800, and positive R$ 4,800. Cash after month three would be R$ 93,600, including the preparation expense already paid.
Actual active customers instead total 20, 35, and 50. Revenue is R$ 6,000, R$ 10,500, and R$ 15,000; variable costs are R$ 1,200, R$ 2,100, and R$ 3,000. Net operating cash outflows are R$ 19,200, R$ 15,600, and R$ 12,000, leaving R$ 61,200. The cumulative shortfall against the planned balance is R$ 32,400. Customer growth has continued, but too slowly to support the original spending plan.
Read cash as time available to learn and act
The remaining R$ 61,200 does not, by itself, show how long the business can continue. Commitments, collection timing, and unavoidable payments matter. An invoiced subscription that has not been collected cannot pay wages. An annual contract reported as a sale may bring cash in installments. The previous example deliberately simplified these differences; a working cash forecast must restore them and distinguish expected receipts from available funds.
Suppose fixed monthly expenses can fall from R$ 24,000 to R$ 18,000 after month three, with a one-time transition expense of R$ 3,000 in month four. At R$ 240 contribution per customer, operating break-even becomes 75 customers: R$ 18,000 divided by R$ 240. The reduction improves room to act, but the transition consumes cash before delivering its full benefit. Check that lower expenses still allow adequate service.
In a recovery scenario, active customers reach 65, 75, and 85 in months four, five, and six. Monthly contributions are R$ 15,600, R$ 18,000, and R$ 20,400. After reduced fixed expenses and the transition payment, cash falls to R$ 55,800 in month four, stays there in month five, and rises to R$ 58,200 in month six. Recovery does not erase the earlier loss or restore the original cash position.
Also prepare a weekly view of near-term payments, separating available cash from committed amounts. Establish a decision reserve before needing it: funds to meet obligations, support customers, and implement an orderly reduction or closure. That reserve constrains the experiment budget. Without it, commercial attempts may consume the very resources needed to change course, leaving a viable decision impossible to execute in time.
Locate the break before choosing an intervention
Follow the whole customer journey. Limited reach among suitable businesses suggests a distribution problem. Many visits without interest may indicate weak messaging or the wrong audience. Evaluations that fail to become contracts require investigation of decisions, price, and perceived risk. Contracts without use point toward implementation. Initial use followed by abandonment raises questions about whether the benefit continues.
For the inventory system, an interview with a shop that declined may reveal that the owner liked the proposal but excluded the employee who would operate it. “I will think about it” concealed an incomplete operational decision. Another shop may decline because a simple existing procedure works well enough. Both losses look similar in a sales report, yet one may need broader participation while the other may have little reason to change.
Observe real tasks with consent. Ask customers to perform an operation and explain their choices without the salesperson taking over at every difficulty. Record where they stop, what information they seek, and what mistake they fear. Respect privacy during observation: use fictional data where possible and limit access to shop information to what the test requires. Assistance should not conceal a task customers cannot complete independently.
Combine interviews, usage records, support information, and lost-sale reasons. No source tells the entire story. Customers may cite price to end a conversation; salespeople may blame the product to protect their evaluation. Conclusions become stronger when different evidence converges. When sources disagree, retain that uncertainty and design an observation that could resolve it instead of selecting whichever explanation best supports an existing preference.
Separate execution defects from changes customers do not want to make
Some obstacles have direct fixes: registration fails, billing is poorly explained, or an import rejects valid files. Others show that adoption demands more effort than customers believe the benefit warrants. For a small shop, reorganizing product records, training employees, and changing routines can consume more attention than expected. This burden exists even when the software works correctly and its features perform as described.
Map the path to the first result and identify dependencies. Requiring thousands of items to be entered before any benefit concentrates effort at the start and value in the future. Starting with a category suffering substantial losses may reduce that barrier. The narrower scope must keep data understandable and avoid creating a misleading picture of total inventory. A partial implementation needs clear limits on the conclusions users can draw.
Assisted implementation can reveal whether the obstacle is operating capacity or insufficient value. Include its cost, however. A customer paying R$ 300 monthly may be uneconomic to acquire if starting requires many specialist hours, even when conversion improves. Measure staff time, rework, and support after the first week. Distinguish temporary learning effort from assistance that every new customer will continue to need.
Avoid automating a routine whose usefulness remains unproven or building integrations to compensate for an unclear offer. First establish whether a controlled manual process delivers the intended result for a small group. Then assess automation, security, and maintenance. Disclose manual work honestly: the test must not hide permanent dependence on people or present an unfinished process as an available automated feature.
Choose experiments that can change a decision
A useful experiment starts with a specific uncertainty and ends with a possible decision. “Improve the experience” is too broad. “Simplify initial importing to see whether more shops record their first movement” identifies an intervention and measurable behavior. Set the observation period, cost ceiling, and results that would justify keeping, revising, or abandoning the change before the experiment begins.
Suppose 12 of the first month's 20 customers reached the defined activation event, an observed proportion of 60%. The team could offer assisted implementation to new customers and measure activation, time to activation, and support hours. Comparisons require care: business size, acquisition source, or motivation may differ. A small group provides useful signals but cannot remove uncertainty or establish that assistance caused every improvement.
Do not change price, audience, messaging, and implementation simultaneously if the purpose is to learn each component's effect. A package of changes may sometimes be necessary to stop losses; acknowledge that the comparison then evaluates the package. Choosing one favored change after results arrive does not establish causality. Record other changes and unusual circumstances so later decisions reflect what the test actually examined.
Assign a budget and a relative review point, such as the end of two weeks of observation. A limited experiment might have a hypothetical R$ 2,000 ceiling if unrestricted cash allows it. Include internal hours and discounts, not only external payments. If the ceiling is reached without adequate evidence, reformulating the question may be appropriate. Repeated extensions turn unresolved uncertainty into recurring expense.
Adjust audience and channels without mistaking activity for progress
The same solution may have different value for neighboring segments. A shop with recurring losses and stable staff may adopt inventory software more readily than a very small retailer whose owner manages everything from memory. Look for mechanisms: problem intensity, implementation capacity, purchasing authority, and frequency of use. Selecting only businesses that praise the presentation produces a convenient sample with little diagnostic value.
Compare channels through customers who remain, full acquisition costs, and time until collection. Referrals may bring fewer but better-matched prospects; advertising may increase evaluations without purchase intent. Acquisition cost should include media, commissions, and attributable sales effort. Recovery of that cost depends on contribution actually received. A signed contract alone cannot establish how quickly the acquisition spending will return.
In the example, monthly contribution is R$ 240 per customer before fixed expenses, using the assumed R$ 60 variable cost. If acquiring one shop costs R$ 720, recovering that spending takes three months of contribution, ignoring cancellations, nonpayment, and financing costs. A customer leaving earlier may never cover acquisition. Additional implementation or support costs change the calculation and must be shown rather than absorbed invisibly.
Refocusing market entry may mean concentrating on one type of retailer and pausing channels that consume support without producing use. Set limits around this concentration: dependence on one partner, seasonality, and restricted segment access can create fragility. The best channel in an early sample is not necessarily an unlimited source of equally suitable customers at the same cost. Reassess as volume and customer composition change.
Use pricing and negotiation to test value without concealing losses
Price often appears in refusals because it is easy to communicate. Before discounting, investigate the comparison: another system, manual work, migration risk, or doing nothing. A shop may find R$ 300 affordable and still fear disrupting operations. Reducing the fee does not resolve that concern and may remove resources needed for effective implementation. Ask what would have to become clearer or easier for the decision to change.
Reducing the price from R$ 300 to R$ 240 while retaining R$ 60 variable cost lowers contribution from R$ 240 to R$ 180 per customer. With R$ 18,000 fixed expenses, operating break-even rises from 75 to 100 customers. Higher sales volume can produce less total contribution unless volume and retention compensate. Make this relationship visible before approving discounts, and include any extra service obligations attached to the offer.
Negotiation can address initial scope, implementation timing, and responsibility for tasks. If promotional terms apply, clearly state their duration, subsequent price, and eligibility. Avoid invented urgency and hidden charges designed to improve conversion. Collecting money early also creates future service obligations. Cash in the account is not automatically an earned result, and spending it without considering those obligations can create a later shortfall.
Define who may grant special terms and the maximum cost they may authorize. Salespeople should not promise integrations without agreement from product and operations. Technical teams should explain alternatives and effort instead of rejecting requests merely from internal preference. Record agreements and compare these customers with the wider base to identify discounts that attract fragile contracts or commitments the business cannot economically maintain.
Build adverse scenarios and triggers before they become necessary
Recovery should not be the only reference. Return to R$ 61,200 at the end of month three, reduced fixed expenses of R$ 18,000, and the R$ 3,000 transition expense in month four. In an adverse scenario, active customers fall to 45, 40, and 35 in months four, five, and six. These are total active balances, potentially reflecting cancellations exceeding new customers, rather than numbers of new purchases.
Monthly contributions become R$ 10,800, R$ 9,600, and R$ 8,400. Month four consumes R$ 10,200, including transition, leaving R$ 51,000. Month five consumes a net R$ 8,400, leaving R$ 42,600. Month six consumes R$ 9,600, leaving R$ 33,000. Expense reductions slow the loss but do not offset a customer base that keeps shrinking. The scenario shows why a cost cut alone cannot establish viability.
If R$ 24,000 is reserved for obligations and an orderly exit, only R$ 9,000 of the final balance lies above that reserve. This does not automatically authorize spending the difference. Upcoming payments, omitted costs, and collection delays may reduce the margin. Decisions must precede loss of access to the money and account for implementation time. A reduction requiring several weeks cannot safely wait until its funding is nearly exhausted.
Combine behavior and cash in decision triggers: cancellations sharing a cause, no improvement after a correction, or projected cash approaching the reserve. A trigger may pause expansion, reduce scope, or begin orderly closure. Avoid automatic rules based on a single month. The purpose is to bring discussion forward and assign responsibility while preserving judgment about evidence, timing, customer obligations, and the available alternatives.
Assign responsibilities and record decisions when views differ
Weak adoption often generates competing explanations. Sales wants lower prices, product wants more development, and operations wants fewer customers until support stabilizes. Each team sees a real part of the problem and may also defend its own incentives. Establish a review process in which claims can be tested against evidence without turning the discussion into blame. A disagreement is useful when its assumptions become visible.
Assign concrete responsibilities. Sales records losses and negotiated terms; product monitors activation and use; operations measures implementation, support, and failures; finance forecasts collections and commitments. One person consolidates the diagnosis, and a clearly identified authority approves changes affecting cash. Small teams may combine roles, but separate records help preserve the different perspectives and expose trade-offs that otherwise remain implicit.
Suppose sales proposes a general discount while product favors improving imports. Two limited tests may resolve the dispute if volume and budget permit; otherwise prioritize the best-documented obstacle. Record each argument, what evidence would change the team's position, and the chosen decision. Retaining disagreement makes later review more honest because the reasoning cannot simply be rewritten to match the outcome.
Each review should end with actions, owners, limits, and the next review point. Include measurement failures and significant complaints even when they disrupt a positive narrative. Rewarding only new contracts can encourage sales beyond implementation capacity. Incentives that also reflect activation and retention may help, but monitor for hidden cancellations, selective reporting, or artificial indicator definitions that make results appear stronger.
Replan development and protect the trust of existing customers
After a disappointing launch, feature lists often expand: each refusal becomes a request, and every request seems like a lost sale. The result may be a more complex, expensive product that is harder to adopt. Prioritize development by the observed obstacle, number of affected customers, and expected effect on use. Removing a recurring failure may be more valuable than adding a prominent feature requested by one prospect.
Separate defects that prevent contracted service, improvements that reduce effort, and expansions serving a different audience. Significant defects need treatment proportionate to their impact; expansions must compete with other hypotheses for budget. Write acceptance criteria in operational language. “Improved importing” is vague; “a valid file is processed with clearly identified rejected records” creates something the team can actually verify.
Existing customers should not silently fund a change of direction through deteriorating support, outages, or unexpected feature removal. Explain scope reductions, impacts, alternatives, and applicable terms clearly while respecting contracts. Consider data export, minimum continuity, and billing treatment. An economically necessary decision can still create costs and responsibilities, which belong in the forecast rather than being treated as someone else's problem.
Control the operational burden left by experiments: temporary access, manual adjustments, customer-specific settings, and individual promises. After each experiment, incorporate what worked, remove what no longer serves a purpose, and record remaining exceptions. Learning improves the business when it reduces uncertainty without leaving an unmanageable operation. Greater adoption built on invisible workarounds can make service delivery unsustainable instead of strengthening the company.
Make additional funding conditional on evidence
Seeking funds during weak adoption may make sense when the shortfall has a verifiable explanation and the money has a defined use, such as correcting an observed implementation barrier and following a new customer group. A request is weaker when it merely preserves the existing structure until sales improve. More cash extends the time available; it does not establish demand or repair an offer whose value customers do not recognize.
Organize the project around its problem, audience, evidence, budget, owners, scenarios, and stopping criteria. Potential funders can then assess what the money is intended to test and what losses are possible. KEZS connects entrepreneurial projects and potential funders through technology and intermediation. Structured project information can support analysis, while investors and other funders remain responsible for their own diligence and independent decisions.
KEZS does not assign a credit score, and presenting a project is neither approval nor a guarantee. Loans create payment obligations; equity changes ownership rights and governance; convertibles depend on contractual conditions; eligible existing receivables differ from hoped-for sales. Each creates different rights and risks. A donation to a nonprofit is not an equity investment or a promise of financial return, and should never be represented as one.
The structure must fit the intended Brazilian transaction. A MEI cannot admit equity partners while remaining a MEI. Public securities distribution and regulated financial activities require appropriate structures and providers; technology or a CNAE classification is not permission. With qualified advice, compare costs, conflicts, obligations, and potential losses. There is no guarantee of approval, repayment, profitability, liquidity, or capital availability to cover the shortfall.
Document evidence without exposing customers or treating records as guarantees
A useful decision file allows others to reconstruct what was known when a choice was made. Retain forecast versions, indicator definitions, experiment results, and reasons for changes. Separate observed figures from estimates and identify collection limitations. An isolated payment establishes a transaction, not retention, satisfaction, or future revenue. Preserving that distinction supports more reliable discussions with staff, owners, and potential funders.
Customer information needs a defined purpose and controlled access. Share only what evaluators need, preferring aggregate information or documents with personal data removed where that supports analysis. Assign responsibility for granting access, recording disclosures, and ending permissions. Demonstration recordings, contact lists, and commercial documents should not circulate freely merely because they help explain the launch. Consider whether less detailed evidence can answer the same question.
If a solution uses blockchain to record integrity, a record may help detect changes to content after a particular point. It does not establish that the original information was true, that legal title exists, that reserves are solvent, or that payment will occur. Do not place private documents on public blockchains. Assess cost, correction mechanisms, and whether the architecture supports appropriate data handling before choosing it.
Brazilian institutional materials on correspondents, securities, funds, MEI, and data protection can be reference entry points for specialist clarification. They do not establish a platform's authorization or validate a particular contract. Disclose commercial relationships and compensation that could influence recommendations. Transparency includes identifying what has not been checked, the uncertainty that remains, and who is responsible for each stage of evaluation.
End each cycle with a concrete choice and conditions for review
At the end of a review cycle, choose whether to continue, correct an obstacle, narrow the offer, reduce operations, or close in an orderly way. Connect the choice to evidence, cost, and time. “Keep trying” does not explain what changes. “Test simplified implementation with a defined group within the approved budget before expanding acquisition” creates an action whose execution and result can be checked.
In the example, reducing fixed expenses to R$ 18,000 is sustainable only if service quality remains adequate and expected contribution materializes. Recovery ends month six with R$ 58,200; the adverse scenario ends with R$ 33,000. Neither result is a probability or promise. They show the consequences of assumptions and identify signals to watch while there is still room to act. Updating assumptions should update the decision, not merely the spreadsheet.
Prepare a one-page decision record showing active customers, activation, retention, contribution, available cash, commitments, and the main unresolved question. Add the approved change, its owner, and the result required to justify the next step. Keep supporting detail accessible for reconciliation. The short document helps coordination; its credibility depends on records that allow the figures and definitions to be checked consistently.
The practical work is to correct measurement, hear from customers who declined or left, test the priority obstacle, and update cash before accepting new expenses. Weak initial adoption may expose a repairable problem or constrain the proposal's viability. Better decisions come from accepting both possibilities and preserving the resources, contracts, and trust needed to respond to what is learned. Past spending alone is not a reason to spend again.
Frequently asked questions.
How long should I wait before concluding that adoption is below what the business needs?
Use a window that gives customers a real opportunity to evaluate and use the solution, together with the time the cash position permits. Daily-use products reveal some signals sooner than services tied to monthly closing. Define the window before reviewing results and compare groups with similar exposure. Serious contracting or functionality failures justify immediate action, while retention requires observation. State what has been measured and which behaviors cannot yet be assessed. Waiting longer is useful only when the additional observation can inform a decision the business can still afford to execute.
How can I distinguish insufficient demand from insufficient publicity?
Examine how many suitable prospects received and understood the offer. If few intended customers had meaningful exposure, evidence about demand remains limited. If many businesses with the problem evaluated and declined, investigate benefit, switching effort, price, and trust. Previous spending on alternatives and attempts to solve the problem provide stronger signals than praise alone. They still do not guarantee purchase of your offer. Use them to design a better test, checking whether prospects recognize the problem, can implement the solution, and will pay under economically workable conditions.
Can free access help recover adoption?
It may help test comprehension and use when payment blocks the initial experience, but it changes the question. Free use does not establish willingness to pay or support the economics of a paid service. Define duration, included support, and the route to a paid contract without unexpected charges. Compare activation, continued use, and subsequent paid conversion. If free access attracts people without the problem or requires extensive assistance, user numbers may rise while evidence quality and cash deteriorate. Include that assistance and any discounts in the experiment's cost.
Should I cut commercial spending when sales fall short?
Assess each expense by what it delivers and the time until collected contribution. Cutting a channel that attracts suitable customers can worsen the problem; maintaining campaigns that produce contacts without useful adoption also consumes correction funds. Preserve enough capacity to observe the market and serve customers. Account for penalties, commitments, and lost knowledge when reducing spending. In the example, lower fixed expenses require a transition payment, so future savings must be weighed against immediate cash use. A reduction is helpful only if the remaining operation can deliver its commitments.
When is changing the target audience justified rather than an escape from the problem?
A change has support when another group demonstrably experiences the problem more intensely, can implement the solution, and accepts viable payment terms. Encouraging conversations after rejection by the original audience are insufficient. Test a defined segment and count adaptation, acquisition, and support costs. Check whether the revised offer fits the company's capabilities and whether concentration creates new dependencies. Repeatedly switching audiences before completing tests prevents cumulative learning and can multiply costs. Record which original assumption the change addresses and what evidence would justify continuing with the new group.
How should weak adoption be presented to a potential funder?
Present the shortfall with reconcilable figures, original assumptions, and explanations still being tested. Show what changed, the cost of the next step, and the conditions that would stop spending. Include an adverse scenario, existing obligations, possible losses, and the rights created by the proposed funding instrument. The aim is an informed decision, not the elimination of perceived risk. Potential funders perform their own diligence and may disagree with the interpretation. Clear documentation can improve analysis but does not secure approval, favorable terms, repayment, or available capital.
When can closing be a better decision than continuing?
Closure may be appropriate when relevant tests fail to support sufficient benefit, customers do not remain on economically viable terms, or another attempt threatens the funds needed to meet obligations. Plan communication, contracts, remaining support, data handling, and payments. A reserve reduces improvisation but does not remove responsibilities. Money and effort already spent do not, by themselves, justify further spending. Compare the alternatives available from this point forward, including their costs, uncertainties, and effects on customers, staff, and owners. Begin early enough to carry out the chosen alternative responsibly.
References and context
Institutional reference points for checking applicable rules and guidance. Calculations and scenarios are original examples, not quotes, historical results or individualized recommendations.
- Banco Central — correspondentes no País ↗
- CVM — Resolução 88, texto e alterações ↗
- CVM — Resolução 175, fundos de investimento ↗
- Portal do Empreendedor — perguntas sobre MEI ↗
- ANPD — orientações e perguntas frequentes ↗
AI-assisted educational content. Decisions require verification of the information, instruments and providers in each actual case.
