A program that prepares entrepreneurs, develops products, supports sales and may also invest brings different activities into one commercial relationship. Investors need to understand what each party will deliver, who will pay and how the work should help the project. Meetings, mentoring and introductions can be useful, but attendance does not demonstrate technical progress, revenue or reduced risk. Monitoring must connect the resources consumed with observable changes in the business and explain the limits of that connection.
Investors must follow two connected operations
At least two operations require attention: the provision of services and the deployment of capital. Services involve scope, price, quality and responsibility for deliverables. Capital involves economic and governance rights, disbursement conditions and exposure to losses. These operations can coexist, including between related parties, but neither replaces the other. Development hours do not automatically become cash invested, and paying for a program does not, by itself, give the payer an ownership interest in the business receiving support.
Start by mapping the relationships among the project company, accelerator or venture builder, actual service provider, investor and decision makers. For each relationship, identify the governing instrument, obligation, compensation and expected evidence. This makes it easier to spot situations in which a program sells services to a company while negotiating ownership in it. Monitoring should support informed decisions to continue, correct course or stop. Documented progress makes those decisions easier to examine; it does not turn the project into a promise of repayment or return.
Turn the program's thesis into a verifiable plan
A program's thesis may promise to improve the product, professionalize management or accelerate market entry. Monitoring requires a defined starting point: which version works, which customers already pay, which tasks remain manual and what the team can actually do. Separate recorded facts from open hypotheses. An interview establishes what someone said, while a signed contract establishes an obligation. Neither alone proves recurring use. Without this baseline, later reports may describe activity without showing whether the underlying situation improved.
Each workstream should address a meaningful uncertainty. Financial preparation might produce a reconcilable budget; development might complete a critical workflow; commercial support might test whether specific customers will agree to buy. Record the proposed causal chain: a deliverable enables a test, the test produces evidence and the evidence informs a decision. This also clarifies why the work matters. If nobody can explain how an activity relates to the project's risks, review the expense before placing it in the schedule.
The plan must state its dependencies. An integration may require customer access, a sale may depend on the buyer's internal approval and implementation may take substantial founder time. The program controls some tasks and merely influences others. Distinguishing the two avoids demanding outcomes nobody can guarantee, while preventing external factors from becoming a blanket excuse for delay. A milestone should reveal what was controllable, what happened, which dependency remained unresolved and what decision the available evidence still permits.
Services, equity, convertibles and debt need separate records
Before reviewing indicators, investors must understand the instrument behind their exposure. Equity may provide ownership and associated rights, subject to the agreed terms and legal structure. A convertible establishes conditions for possible conversion and other contractual rights. Debt creates payment obligations under its instrument. Milestone monitoring can inform all three, but it does not equalize their risks, treatment in adverse situations or exit mechanisms. Receivables financing also depends on identifiable rights and collection conditions; it is not interchangeable with equity or an unsecured promise to pay.
A service contract should specify whether compensation is payable in cash, recognized as an obligation or handled through another expressly defined mechanism. If services are exchanged for ownership, examine the applicable legal and corporate structure, valuation and delivery conditions. Listing a commercial price in a presentation and calling it an investment is insufficient. Check whether the same services also attract cash charges. Otherwise, the company may face duplicate payment or dilution without an identifiable contribution, while reports overstate the resources actually made available.
In Brazil, the business form and activity matter. A MEI, the individual microentrepreneur category, cannot admit equity partners while retaining MEI status. A donation to a nonprofit is neither an equity investment nor a promise of financial return. Public securities offerings and regulated financial activities require appropriate structures and participants. Technology or a CNAE economic activity classification does not provide permission. Responsible professionals should assess these issues before monitoring treats an assumed right as valid. Recording a transaction cannot cure an unsuitable legal structure.
Value services without manufacturing invested capital
Valuing services begins with defining what will be purchased. A development proposal should identify functions, acceptance criteria, documentation, maintenance and dependencies. A commercial proposal should distinguish lead generation, qualification, negotiation support and responsibility for closing sales. Comparable offers, estimated effort and specialist expertise can inform pricing, but the price must match the scope. A list of professional names and hours does not prove the project will receive a usable asset or a capability its own team can maintain.
Keep three values separate: the price charged to the project, the provider's estimated cost and the economic benefit the work might generate. These figures need not match. The provider may earn a legitimate margin, the project may receive a discount and the benefit may fall short of expectations. This distinction becomes especially important when the venture builder also holds equity. It may earn service revenue while an investor loses money on the ownership interest. The analysis should make that combination of incentives visible.
Consider a hypothetical proposal for R$ 120,000 in services, assessed against alternatives with equivalent scope. The conclusion might be that the price is reasonable, excessive or impossible to compare because details are missing. Even a favorable assessment does not turn R$ 120,000 into cash available for salaries or suppliers. Ask which deliverables justify the price, how acceptance works and what happens to unperformed portions. An approved value is a contractual reference subject to execution, not advance proof of benefit or evidence that cash entered the company.
A numerical example separating cash from services
Consider a hypothetical software project for commercial operations, monitored over six months. Its plan provides R$ 300,000 in cash and a separate venture builder service package valued at R$ 120,000. The cash budget allocates R$ 150,000 to team and product, R$ 60,000 to commercial testing, R$ 30,000 to infrastructure and security, R$ 30,000 to administrative and legal support, and R$ 30,000 to a reserve. These five categories total R$ 300,000. The service package is outside that cash balance and cannot pay those expenses.
The services comprise R$ 24,000 for preparation and governance, R$ 60,000 for specialist development and knowledge transfer, and R$ 36,000 for commercial support. Each portion has its own scope and acceptance process. In this example, the builder undertakes the work without charging the project cash and negotiates ownership through a separate instrument, conditional on delivery and assessment of the applicable structure. The investor's R$ 300,000 cash contribution also has its own instrument. Adding the values does not establish an ownership split.
The plan may describe R$ 420,000 in planned resources if it clearly distinguishes R$ 300,000 in cash from R$ 120,000 in contractually valued services. Calling the whole amount an investment without explanation could suggest liquidity that does not exist. All figures are hypothetical arithmetic, not market prices or expected returns. The useful question is whether this combination provides enough capacity to test the project, with costs, negotiated dilution and execution risks visible. Headline resource totals cannot answer that question without the underlying composition and obligations.
Design milestones that support concrete decisions
In the example, the R$ 300,000 will be made available in three installments of R$ 100,000 under the funding instrument. The first starts the work. The second depends on assessment of the milestone at the end of month two, and the third on the milestone at the end of month four. The passage of time does not automatically trigger release. Specify who decides, what evidence they receive and how partial completion, justified delay and changes to the working hypothesis will be handled.
The first milestone could require a reconciled budget, a critical product workflow demonstrated in a test environment and documented interviews with prospective customers in the selected segment. These provide different evidence: financial organization, technical execution and commercial insight. The second milestone might require a controlled deployment, observed use by participating customers and analysis of support costs. None alone establishes scalability or profitability. Acceptance should reflect the stated question, rather than allowing one successful activity to conceal an unrelated unresolved requirement.
For each milestone, define mandatory criteria, tolerances and consequences. A defect exposing private data may require use to stop until correction. A small commercial sample may justify a limited extension with capped spending. Decisions should weigh the significance of the deviation and the cost of learning more, avoiding both convenient release and mechanical cancellation. Disbursement conditions must be supported by the contract. A monitoring spreadsheet cannot unilaterally create rights to suspend payments, change obligations or impose requirements that the parties never agreed.
Cash flow: decision time also consumes resources
The first month uses R$ 45,000: R$ 25,000 for team and product, R$ 8,000 for commercial testing, R$ 4,000 for infrastructure and R$ 8,000 for administrative and legal support. Month two also uses R$ 45,000, divided into R$ 25,000, R$ 10,000, R$ 5,000 and R$ 5,000 across the same categories. The initial R$ 100,000 installment therefore leaves R$ 10,000 at the end of month two. That balance is cash remaining, not the total financing agreed or the value of services still to be delivered.
If the second installment arrives before the next commitments fall due, month three begins with R$ 110,000. Months three and four each use R$ 45,000, leaving R$ 20,000. The third installment raises available cash to R$ 120,000. Months five and six each use another R$ 45,000, leaving a R$ 30,000 reserve. Total consumption is R$ 270,000. Builder services remain outside this calculation, and the projection does not require future revenue to balance. The arithmetic assumes the stipulated installments actually arrive when needed.
If assessment of the first milestone takes an extra month, the remaining R$ 10,000 cannot cover planned monthly spending of R$ 45,000. Maintaining that pace leaves a R$ 35,000 shortfall. This calls for an early decision on expense reductions, schedule changes or another expressly negotiated solution; additional funding cannot be assumed. Submit the decision package before commitments fall due, with a known review period. A rigorous review that ignores payment timing can cause an avoidable cash crisis even when the broader funding plan appears sufficient.
Reconcile the budget, execution and outstanding commitments
Financial reporting should distinguish approved budget, expense incurred, payment made and future commitment. An issued invoice may remain unpaid, a signed engagement may create later payments and an advance may precede completed work. Treating all of these as spending obscures cash needs. Showing only payments hides obligations already undertaken. Reconciliation must preserve the distinctions without making the report unreadable. Investors should be able to move from the reported balance to supporting records and understand what cash is available after known commitments.
In month three, the R$ 45,000 comprises R$ 25,000 for team and product, R$ 10,000 for commercial testing, R$ 5,000 for infrastructure and R$ 5,000 for administrative and legal support. Across six months, team and product receive R$ 25,000 monthly. Commercial testing receives R$ 8,000, R$ 10,000, R$ 10,000, R$ 10,000, R$ 11,000 and R$ 11,000. Infrastructure receives R$ 4,000, R$ 5,000, R$ 5,000, R$ 5,000, R$ 5,000 and R$ 6,000. Administrative and legal support receives R$ 8,000, R$ 5,000, R$ 5,000, R$ 5,000, R$ 4,000 and R$ 3,000.
These schedules exactly match the approved category totals and maintain R$ 45,000 of monthly consumption. Actual differences should be explained through quantity, price or scope changes. If a tool becomes more expensive, show the impact and proposed offset. If an expense is reclassified, preserve the history and reason. The R$ 30,000 reserve must not quietly absorb overruns to make performance look unchanged. Its use should follow the agreed decision authority and update the remaining projection, including the effect on the company's room to respond to later problems.
Technical and commercial evidence needs explicit limits
Evidence quality depends on the question. Verifying technical delivery may require a reproducible demonstration, test records, an identified version and appropriate access to the code. Adoption records should distinguish invited users, active users and meaningful actions. Revenue analysis must separate proposals, contracts, invoicing and cash collection. A screenshot can support discussion but rarely establishes functionality, repeat use or ownership by itself. Evidence should be traceable to the claim being tested, with enough context to explain what it does and does not demonstrate.
Commercial support deserves particular care because activity is easily mistaken for progress. One hundred contacts are not one hundred opportunities. Reports can distinguish suitable prospects, meetings held, problems confirmed, proposals issued and reasons for losses. Stage definitions should remain stable throughout the comparison period. If they change, restate the series or identify it as noncomparable. The aim is to understand the buying process and its obstacles. A visually attractive funnel is of little value if its stages combine different meanings or conceal weak qualification.
Testing a claim that a customer task takes less time requires a baseline, an observed task, identified participants, a test duration and stated limitations. A small pilot may suggest usefulness without establishing a broad market. A sale driven by a personal relationship may not be repeatable. Existing eligible receivables must also be distinguished from hoped-for sales: commercial expectations do not create equivalent collection rights. A narrow, verifiable conclusion gives investors a stronger basis for decisions than an expansive claim supported by weak or incomplete evidence.
Deliverables and intellectual property must outlast the program
A product deliverable helps the project only if the company can use, maintain and develop it. Contracts should identify code, documentation, models, commercial materials, data and other expected outputs, with their rights and restrictions. Distinguish the provider's preexisting assets, third-party components and work created for the project. Paying for development does not automatically resolve intellectual property ownership. The chain of rights must include the professionals and suppliers who actually contributed, rather than relying solely on an agreement with the program's main contracting entity.
For the R$ 60,000 specialist development package, acceptance might cover a functioning component, installation instructions, relevant tests and knowledge transfer to the team. Assess technical dependencies and ongoing costs as well. If the solution works only through an account controlled by the builder, the project could lose operational access when the relationship ends. Define administrative access, data export, repository transfer and use of external services, subject to security and applicable contracts. A successful demonstration does not establish that the company can independently operate what it receives.
Legitimate negotiation remains possible. The builder may wish to retain a reusable library, while the project needs enough freedom to operate without permanent commercial dependence. A suitable license may resolve part of that tension; project-specific components may need different treatment. Investors should assess the economic consequences, including future diligence or a company sale. Acceptance records should state what was received and which limitations remain. Temporary access to a tool, possession of a code copy and full legal ownership are different positions with different practical consequences.
Conflicts of interest: disclose, separate and decide
Combining services and ownership can align interests, but it also creates conflicts. A builder may recommend a purchase that increases its own revenue, favor further development when commercial evidence supports simplification, or approve its own work to trigger compensation. An investor connected to the program may enjoy preferential information or terms. Shared enthusiasm for the project's success does not resolve these issues. Identify the decisions in which one party's benefit may diverge from the interests of the company and other participants, including decisions about how scarce resources are allocated.
A proportionate process records relevant relationships, prices and approval authority. Related-party engagements may require comparable scopes and a documented justification. When acceptance has material economic consequences, the person delivering the work should not be its sole evaluator. Depending on the structure, recusal or assessment by someone without the same incentive may be appropriate. These controls cost time and money and should be sized accordingly. Without them, participants may struggle to distinguish an ordinary operational error from preferential treatment or an unsuitable commercial arrangement.
Conflicts also arise in allocating opportunities and capacity. A program may support competing businesses or assign the same team to several projects. Examine confidentiality, service capacity and the use of learning without assuming unlimited exclusivity. Referral compensation involving suppliers or funders should be transparent when relevant to the decision. Recording a conflict does not remove it; disclosure helps participants assess whether its management is acceptable. If the divergence cannot be managed, declining the engagement may be the more economically coherent choice, even when the proposed work has apparent benefits.
Assign operational roles and keep decisions proportionate
A workable routine gives named people clear responsibilities and authority. Project leadership explains priorities and remains responsible for running the business. The financial lead reconciles payments and commitments. The builder reports contracted work and dependencies. The investor or competent governance body considers decisions assigned by the instruments. Specialists can review defined technical or legal questions. This division helps prevent one person from producing the figures, validating the deliverable and authorizing their own compensation without review, while keeping accountability for business execution clear.
The cadence can combine brief operational updates, monthly financial closing and formal assessments at disbursement milestones. A decision package should contain cash position, forecast, accepted deliverables, deviations, new risks and a specific proposal. Supporting detail should remain accessible under suitable confidentiality arrangements. Long meetings cannot compensate for irreconcilable numbers. Record refusals and conditional decisions as well as approvals, with a responsible person and correction deadline. The next discussion should begin with the previous agreement and its outcome, rather than depending on participants' recollections.
Monitoring consumes staff time, tools and specialist review, so include it in the budget and adjust it to risk, complexity and the rights involved. A different handcrafted report for every investor can take time away from product work and sales. A common information package with appropriate supplementary access is often more useful. Proportionality means concentrating effort on information that could change a decision and reducing tasks that merely repeat it. It does not mean abandoning controls, accepting unsupported claims or giving every participant unrestricted access to sensitive material.
Resolve disagreements without erasing the history
Suppose that by the end of month four the product is deployed, but customers use only part of the intended workflow. The builder argues that more features are needed, the commercial team questions the value proposition and the investor considers withholding the third installment. All three positions may be plausible. State what each explanation predicts and which low-cost test could distinguish them. Contractual authority and the quality of a hypothesis are related but separate matters. Having the right to decide does not, by itself, establish which explanation is correct.
Renegotiation could redirect some planned work into a narrower test within available resources, with new evidence and a clear deadline. Changes between budget categories require approval under the instrument and an updated forecast. Changes to services require the R$ 120,000 package to show what is removed, what is added and how acceptance changes. Keeping the original description while declaring a different delivery complete obscures the agreement, even if the substitution is useful. The revised plan must also show its effect on dependencies and commitments already made.
The decision record should preserve the original milestone, evidence obtained, differing interpretations and agreed amendment. Equity, conversion and debt terms do not change automatically when the operating plan changes. Economic adjustments need separate negotiation and assessment of their consequences. The outcome may also be to close a workstream or withhold further resources, while respecting existing obligations. Good monitoring does not require finding a reason to continue every time. It makes the basis and cost of each choice understandable, including when further spending is no longer justified.
Prepare responses to adverse scenarios before an emergency
One adverse scenario is rejection of the technical delivery in month two. Depending on the contract, the second installment may remain conditional while only R$ 10,000 of cash remains. First identify the defect and distinguish correction owed by the provider from genuinely new work. If the builder failed to meet the agreed scope, do not assume the project must purchase the same delivery again. Correction periods, reduced activity and the consequences of withheld funding should be addressed before payment deadlines, with decisions grounded in the actual instruments.
Another scenario is losing a test customer or making no sales. Because the base budget does not depend on receipts, the cash plan may remain arithmetically workable while the commercial thesis weakens. The company could finish six months with R$ 30,000 but insufficient evidence to obtain further funding. That reserve does not guarantee continuity. Examine commitments beyond the program, the cost of an orderly reduction in activity and the possibility of losing invested capital. Staying within budget is evidence of financial execution, not proof of business success.
Other problems include a key person's departure, a code ownership dispute, an unavailable supplier or a data exposure. Response plans should identify owners, priorities and necessary information without pretending every contingency is foreseeable. Debt requires its own repayment-capacity analysis. An equity interest may have no buyer, and anticipated conversion conditions may never occur. Useful program deliverables can coexist with no liquidity and no return. No milestone guarantees capital preservation, payment, profitability or an opportunity to exit, and the cost of responding to a problem can reduce remaining resources.
Correct monitoring errors with a traceable record
A recurring mistake is treating the full service package as performed when the contract is signed. In this example, that would report R$ 120,000 of completed work before acceptance. Separate contracted, delivered, accepted and pending amounts using consistent criteria. Another mistake is presenting conditional undisbursed funding as available cash. Correct the cash position and identify which obligations are covered by money actually received. Preserve the earlier report and explain the adjustment so participants can understand both the revised position and the decisions previously made from it.
Metrics can also be duplicated or selected for convenience. Two contacts at one company may become two opportunities, an internal demonstration may be labeled a deployment and one-off revenue may be described as recurring. Correct this through stable definitions, deduplication and review of affected conclusions. If inaccurate information supported a disbursement, revisit that decision and the applicable rights. Quietly changing a dashboard leaves participants unable to understand why their interpretation of the project changed or whether an earlier approval now needs attention.
Distinguish process failure, measurement limitations and indications of improper conduct. Not every deviation warrants an extensive investigation, but repeated patterns, inconsistent documents and resistance to providing support deserve attention. Proportionate responses may include independent review, restrictions on new commitments or replacement of a responsible person, subject to the contracts. Record facts and uncertainties without premature accusations. Early correction preserves decision-making capacity. Concealing a problem to protect the program's appearance can increase later costs and make an otherwise manageable disagreement harder to resolve.
Organize project documentation and close the monitoring cycle
Organizing records by project brings the thesis, instruments, budget, deliverables and decisions into one coherent account. KEZS connects entrepreneurial projects and potential funders through technology and intermediation. Investors conduct their own diligence and make their own decisions; KEZS does not assign a credit score. Transparent documentation can help people ask better questions and make verifiable comparisons. It does not, by itself, establish regulatory authorization, project quality or ability to meet obligations. Its usefulness depends on the underlying evidence, access arrangements and participants' assessment.
Document access should match each participant's role and protect personal data, trade secrets and contracts. Private documents should not be placed on public blockchains. A technological record may help demonstrate integrity or sequence, but cannot establish the truth of its contents, legal title, reserve solvency or payment. Guidance from Brazil's CVM securities regulator, Banco Central, ANPD data protection authority and Portal do Empreendedor provides reference entry points within their respective subjects. Those references do not prove that a platform is authorized to conduct a particular activity.
At closing, investors should receive a reconciliation of cash received, the example's R$ 270,000 in planned consumption, the R$ 30,000 reserve and separate service execution. Actual results may differ and must show those differences. Include rights over deliverables, remaining obligations, hypotheses supported or rejected and the next decision. Continuing, reducing or ending the activity each needs its own justification. Milestone discipline makes the path examinable and can limit poorly informed decisions, while monitoring costs, execution uncertainty and the possibility of loss remain present.
Frequently asked questions.
How can investors compare a program that charges cash with one that asks for equity?
Begin with equivalent scopes, expected quality, rights over deliverables and responsibility for ongoing operation. Then distinguish the known cash payment from the uncertain economic cost of negotiated ownership. That interest could represent a meaningful share of future value or become worthless, depending on performance and terms. Converting it into one fixed price without stating assumptions hides this uncertainty. Include maintenance, dependencies, exclusivity, conflicts and additional service charges. An apparently cheaper program may transfer less usable capability or create later obligations. The comparison should explain what the company receives and what it gives up under each arrangement.
Should investors require advance approval for every expense?
The answer depends on contractual rights and the significance of decisions, but item-by-item approval can delay operations and blur responsibility. A proportionate approach is to approve the budget, categories and decision authority, then monitor execution and reserve specific approvals for material changes, related-party dealings or commitments outside the plan. Negotiate those boundaries rather than assuming the investor manages the company. Frequent monitoring and reconciled information may provide more useful oversight than a queue of small payment requests. The procedure must also allow decisions to arrive before obligations fall due, especially where delayed disbursement could create a cash shortfall.
Does meeting every milestone mean the project is ready for more capital?
No. Milestones establish only what their criteria and evidence support. A team may deliver a product and follow the budget without demonstrating sufficient demand, viable margins or capacity to expand. A new funding decision should examine remaining uncertainties, the cost of the next stage and the rights offered. Check whether the original criteria still matter: a completed plan may have answered a question that has since lost relevance. Meeting milestones is an input to assessment, not a guarantee of financing or return. Available cash, outstanding obligations and the absence of a future buyer or funder still require separate consideration.
How should a useful deliverable be assessed when commercial results fail to appear?
First establish whether the contracted service was delivered and accepted under suitable criteria. Then examine what the commercial test revealed and whether the provider owed a specific result or a clearly defined support activity. A feature can function correctly without solving a need customers will pay to address. This distinction avoids both denying all compensation for an unsuccessful test and rewarding activity of inadequate quality. The next decision should weigh demonstrated learning, reuse potential and the cost of continuing, while preserving contractual consequences. Technical acceptance and commercial validation answer different questions and should remain visible as separate findings.
What if the builder makes code delivery conditional on a new negotiation?
Review the existing agreement on ownership, licensing, access, acceptance and payment. If transfer or access is already owed, address performance of that obligation through the applicable contractual mechanisms. If the subject was left undefined, negotiate a solution while assessing operational dependence, third-party rights and replacement costs. Possessing a copy does not necessarily provide unrestricted use, modification or transfer rights. Preserve evidence and authorized continuity while resolving the dispute, without accessing systems or materials beyond existing permissions. The resulting agreement should clarify what the project can operate independently and which restrictions or ongoing costs remain.
When is an independent review worth its cost?
It is often most useful when a material decision depends on expertise participants lack, a significant conflict exists or evidence is inconsistent. The scope can be narrow: verify an integration, reconcile specific expenses or examine the rights chain for a component. State the review's limitations rather than presenting it as certification of the entire business. Compare its cost with the exposure and the value of the information for the decision. Broad, repeated reviews can consume resources without resolving the issue that determines whether work should continue. A focused review should identify the question, evidence examined, remaining uncertainty and practical implications.
What information should remain available after the program ends?
Preserve instruments, approved amendments, reconciliations, acceptance evidence and relevant decisions under applicable obligations and the retention policy. The project also needs lawful access to deliverables and information required to operate and meet its commitments. Personal data and trade secrets must be handled according to purpose and permissions, rather than retained indiscriminately. Closing records should identify responsibility for outstanding matters, contracted support and conditions for future access. Together, these records explain rights and results without relying on meeting participants' memories. They should also distinguish completed work from unresolved obligations and document any restrictions that continue after the commercial relationship ends.
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.
