An investor assessing an opportunity involving an accelerator or venture builder needs to examine three things together: the business, the program's contribution and the contract allocating costs, rights and risks. A commercially promising project can become unattractive if it accepts obligations its cash cannot support. A capable program may add little when it supplies resources the team already has. The program's reputation cannot replace analysis of this combination.
The opportunity combines a project, a program and a contract
Business preparation, product development, commercial support and investment are different contributions. A workshop may improve decisions without creating an asset the company can transfer or sell. Developers may deliver usable software while leaving technical dependencies. An introduction may open a discussion without generating revenue. Cash actually contributed can fund expenses; service hours provide a particular capacity whose usefulness depends on scope, availability and execution.
The first task is to define the problem the program should solve. Examples include turning a prototype into a product customers can contract for, reducing implementation time or establishing sales practices for a defined customer segment. Broad ambitions such as accelerating growth need observable meaning. Otherwise, proposals offering similar numbers of hours may appear equivalent even though one addresses the main obstacle and another merely adds meetings.
The central question is what evidence supports the belief that these resources, people and terms will help the project reach its next milestone. The answer remains uncertain and may justify rejecting the opportunity. The method makes assumptions, the cost of testing them and the consequences of incomplete execution easier to compare. It supports the investor's independent judgment without promising approval, successful execution, repayment or investment returns.
Source opportunities around needs that can be examined
Opportunities may come through founders, universities, business associations, suppliers, technical communities and commercial networks. Diverse channels can reveal projects beyond the most visible circles, but presentation quality will vary. A well-advised team may prepare better documents than another with stronger customer demand. Record where a referral originated without treating the reputation or relationships of the person making it as automatic evidence of project quality.
A useful initial record identifies the intended customer, observed problem, product stage, team and main obstacle to progress. It also states what the project needs: money, development capacity, commercial access or preparation. Financing delivery under existing contracts raises different questions from funding a business that has yet to discover who will pay. Combining those needs in one undifferentiated pipeline makes subsequent comparisons less informative.
Separate entry requirements from preferences. Having an accountable project lead, clarifying ownership of essential assets and accepting due diligence may be conditions for proceeding. Sector experience, customer concentration and learning speed require contextual assessment. Rejecting every business without revenue may suit an expansion investment strategy but contradict a program designed to test early products. Criteria should reflect the intended milestone rather than an assumed universal definition of readiness.
Evaluate sourcing channels by what happens after referral: adequate documentation, fit with the program and the quality of decisions to proceed or stop. Application volume alone can reward publicity without improving investment choices. Record rejected projects and reasons as well. This history can expose poorly calibrated filters, such as excluding technically sound businesses because their presentations do not use the committee's preferred vocabulary. It also helps distinguish weak sourcing from unsuitable selection criteria.
Compare projects seeking a similar development milestone
Comparison becomes more precise when projects seek a similar milestone. Two businesses with the same revenue may face very different tasks: one must demonstrate contract renewals, while another must reduce implementation costs that consume its entire margin. Revenue alone conceals the work ahead. A milestone should describe an examinable change, such as completing a paid implementation within an agreed amount of staff effort.
A comparison matrix can use five descriptive categories: demand evidence, execution capacity, the program's additional contribution, required resources and contractual risks. For each, record a provisional conclusion, supporting evidence and the main unresolved question. This makes differences discussable without giving an aggregate score an appearance of certainty. A strong overall assessment cannot resolve disputed ownership of the product or make an unaffordable payment obligation disappear.
Describe the strength and limits of evidence. A founder's account of customer interest, a documented conversation, an observed test and a completed paid engagement provide different information. None guarantees the next step. Even a signed contract may depend on conditions being fulfilled or a difficult implementation. State what was actually reviewed, what occurred and what remains conditional, rather than treating every document as evidence of the same maturity.
Consider one project with many prospective buyer meetings and another with fewer contacts but recurring use and a paid contract. A program focused on prospecting could contribute more to either, depending on the actual bottleneck. Investigate why meetings fail to progress and whether observed use can be repeated with other customers at an acceptable cost. Neither meeting volume nor a single successful engagement settles those questions on its own.
Distinguish available capacity from an additional contribution
A program's value depends on the difference between the project's plausible path with its involvement and the path without it. That difference cannot be observed in full, but its assumptions can be investigated. If founders already have competent developers and need commercial implementation support, more programming may add features without improving sales. Additional value comes from matching the offered resource to the constraint blocking the next step.
Ask who will perform the work, how much capacity they will commit and who will supervise it. A list of associated specialists does not establish operational access. Clarify who takes responsibility when problems arise, how many projects share the team and how priorities are assigned. Replacement arrangements for an essential professional should address timing, minimum qualifications and schedule effects. A named expert has limited practical value if no usable availability is committed.
Some contributions create indirect value. An architecture review may prevent rework; guided negotiation may teach a founder to manage later sales discussions. Document the decision produced and the capability transferred. Meetings and hours can measure effort, but they do not establish usefulness. The program should explain why the work matters and how completion will be recognized, including whether the company can apply what it learned without repeated assistance.
Any previous results presented need context and permission for their use. Selected cases may omit withdrawals, teams that arrived with traction or decisive external funding. Investors can request descriptions of work actually performed, selection criteria and recurring difficulties while respecting confidentiality. Where comparable experience is absent, uncertainty is greater. A smaller initial scope, followed by a decision based on evidence, may be more appropriate than assuming a full package will work.
Value services without treating an advertised price as invested capital
Service valuation requires separating production cost, market price and usefulness to the project. The program's internal cost includes people, tools and coordination, but does not alone determine what the company should pay. Market comparisons require similar scopes. Usefulness depends on priority and the ability to use the result. An expensive feature may contribute little if customers do not need it or the team cannot operate it.
Break a package into identifiable items, such as development, product design, commercial preparation and ongoing support. Each should have a scope, deadline, accountable person, acceptance criteria and assigned price. Explain discounts as well. Advertising a package at a stated value and exchanging it entirely for equity does not establish that this amount was invested in cash or that an independent supplier would offer the same work at that price.
External quotations help when assumptions align on team seniority, documentation, security, testing, maintenance and rights to the output. A cheaper offer may omit essential work; a more expensive one may include unnecessary support. Record adjustments used to make proposals comparable. If no suitable alternative exists, the valuation remains a negotiated assumption, and the decision memorandum should say so. Uncertainty about price should remain visible rather than disappearing inside a package total.
Services may be paid for in cash, equity or another appropriate contractual structure, with different consequences in each case. Equity compensation requires defining the obligation, when the right is earned and what happens after partial delivery. Accounting, legal and tax treatment require professional review under the applicable Brazilian framework. Describing the whole package as invested capital obscures available cash and can mislead future investors about both funding received and obligations incurred.
Separate the economic rights created by each instrument
Equity, convertible instruments and debt are not interchangeable versions of one promise. Equity provides rights under the company's legal structure and agreements, with potential loss and no assured liquidity. A convertible depends on conversion rules, triggering events and what happens if conversion never occurs. Debt creates payment obligations that may strain cash even while the product is still searching for demand. The instrument changes the consequences of an unsuccessful business outcome.
Program documents should separately identify cash contributed, services contracted and rights granted for each contribution. If a program supplies cash and also receives equity for execution, there are two economic justifications to examine. Clear separation prevents the same contribution from being counted twice. It also reduces the risk of a founder discovering an additional charge after believing that the equity already compensated all the promised work.
Rights over receivables require identifying existing eligible claims, their debtors, payment conditions and restrictions. Projected sales do not become receivables because they appear in a forecast. Donations to nonprofit organizations create neither equity ownership nor a promised financial return. In Brazil, an MEI cannot admit equity partners while retaining MEI status. A proposed ownership transaction therefore requires an appropriate change of structure before it can proceed on that basis.
Examine how the opportunity will be presented and distributed. Public securities distribution and regulated financial activities require appropriate structures and providers. A technology platform or the inclusion of a CNAE business activity classification does not itself grant permission. Banco Central do Brasil and CVM materials help identify relevant issues, but the actual analysis depends on the participants, contracts and activities. Those references do not establish authorization for KEZS or any specific transaction.
A numerical example: cash, services and ownership
Consider a hypothetical business software company with a legal structure compatible with the proposed transaction. To simplify the arithmetic, its founders hold 1,200,000 ownership units, priced in the negotiation at R$ 1 each. Its value before the new contributions is therefore R$ 1,200,000. An investor contributes R$ 300,000 in cash for 300,000 newly issued units. The resulting 1,500,000 units are held 80% by the founders and 20% by the investor.
The program offers services at a negotiated price of R$ 150,000. The company will pay R$ 50,000 in cash, while R$ 100,000 may be compensated with 100,000 new units, conditional on delivery. Full issuance would increase the total to 1,600,000 units. The founders would hold 75%, the investor 18.75% and the program 6.25%. The investor knows about this anticipated dilution before contributing the cash.
The company receives R$ 300,000 in cash, not R$ 450,000. The R$ 150,000 is the assigned service price: R$ 50,000 consumes part of the cash received, and R$ 100,000 represents conditional equity compensation. This distinction allows liquidity and dilution to be assessed together. Using one price per unit simplifies the example; a real negotiation could use different prices and rights, requiring a fresh calculation rather than reuse of these percentages.
The example contains no options, other ownership classes, convertible debts or special economic rights. Adding any of them would change the analysis. These percentages describe ownership in the simulation and do not guarantee identical proportions in future distributions. Preferences, obligations and contractual events can change economic outcomes. The ownership table must therefore be read alongside the agreements. Every amount here is hypothetical arithmetic, not a market valuation, quoted service price or expected investment return.
The cash schedule can change the investment decision
Keep the hypothetical R$ 300,000 contribution and assume zero opening cash and no revenue during the period. The company pays the program R$ 25,000 at the start and another R$ 25,000 in month three after acceptance of the corresponding work. Operating expenses consume R$ 50,000 each month, excluding program payments so that no expense is counted twice. Services compensated with equity add no cash to the balance.
After the first program payment, cash is R$ 275,000. It falls to R$ 225,000 at the end of month one and R$ 175,000 after month two. Month three consumes R$ 50,000 in operating expenses and the second R$ 25,000 program payment, leaving R$ 100,000. Month four ends with R$ 50,000 and month five with zero. Zero is the mathematical boundary of these assumptions, not a prudent operating position.
Suppose the commercial milestone requires two months of implementation after technical completion, expected in month three. The company would reach its cash limit just when it hoped to demonstrate the commercial result. Implementation delays, late customer payment or slower contracting could make the plan unworkable. The investor must decide whether to reduce scope, change the spending sequence or require a resource structure better matched to the work and timing before investing.
One alternative is a smaller initial delivery that tests implementation before the entire budget is consumed. Another is to renegotiate service payment timing, recognizing that postponement does not eliminate the obligation. Show how each alternative changes time, cost and evidence produced. A future funding round may be possible, but it cannot fill the forecast as though it were already contracted. Expected revenue likewise needs explicit timing and uncertainty rather than automatic inclusion.
Turn service commitments into deliverables with verifiable acceptance
The R$ 100,000 eligible for equity compensation can be divided into three independent deliverables: R$ 40,000 for a documented functional module, R$ 35,000 for a tested implementation package and R$ 25,000 for a commercial process transferred to the team. In this simplified model, each real corresponds to one unit, totaling 100,000 units. Compensation follows accepted work without assuming that the program controls the business's entire development.
The module needs observable criteria: running agreed workflows, handling specified failures and allowing company operation. The implementation package may require documentation, reproducible configuration and assisted execution in an authorized environment. The commercial process may include a priority customer profile, qualification criteria, materials and demonstrated training. A promise of specified revenue would be a different obligation, affected by factors the program may not control. Acceptance criteria should reflect the actual contribution purchased.
Acceptance needs an accountable reviewer, a review period, recorded defects and an opportunity to correct them. The company should not refuse indefinitely because of preferences introduced afterward; the program should not impose acceptance merely by uploading files. Scope changes need a written decision on price, timing and impact on the objective. This protects useful completed work while reducing the chance that every disagreement becomes a dispute over ownership.
If only the first deliverable is accepted and termination creates no additional rights, the program receives 40,000 units. Total units become 1,540,000: approximately 77.92% for the founders, 19.48% for the investor and 2.60% for the program. The R$ 50,000 in cash payments follows its own contractual conditions and does not disappear when other items end. Unearned equity and amounts already payable for services must be considered separately.
Intellectual property rights must support practical use
A deliverable can function while leaving the company unable to use it on secure legal terms. Identify who owns code, designs, text, databases and components created before the contract. Check rights over contributions by employees, contractors and participating partners. Repository access alone establishes neither ownership nor a sufficient license to sell, modify and maintain the product. Operational possession and legal permission answer different questions, both of which matter to investors.
The contract can distinguish the program's pre-existing technology from assets developed specifically for the project. This can preserve reusable tools without trapping the company. If a program library is essential, its license must accommodate intended operations, continuity, maintenance, supplier changes and a possible corporate transaction. Future charges and termination conditions should be visible before investment. An apparently complete handover may otherwise conceal an ongoing dependency with substantial costs.
Technical diligence also examines third-party dependencies and licenses, development data and permissions for training or evaluating AI systems where relevant. Material supplied by one customer does not automatically become available for other program projects. Records of component origins and permissions help reveal restrictions before a customer contract or subsequent funding round exposes them. This review should cover what the team actually uses, rather than rely solely on a general assurance that all materials are proprietary.
Handover should include operating documentation, institutionally controlled access, deployment instructions and recovery capability. Credentials require protected management and controlled transfer, rather than circulation in open documents. The practical test is whether the company's team can operate and develop the result with the autonomy contemplated by the contract. Some continuing dependence may be acceptable if understood, priced and supported by alternatives. Its cost belongs in the assessment of the service's usefulness.
Conflicts of interest require decisions, records and limits
A venture builder may source a project, negotiate its valuation, provide services, hold a governance position and receive equity. This combination can align execution with outcomes, but also concentrates influence. A conflict arises when someone recommending a purchase benefits directly from its approval. Disclosure is necessary but insufficient: the decision needs criteria and scrutiny by someone who does not share the same economic incentive.
Relevant relationships include suppliers connected to managers, referral compensation, interests in competing companies and benefits triggered by transaction completion. Investors should understand who receives what, on which event and from whose resources. If purchasing services is a condition of receiving investment, make that link explicit. It can restrict supplier choice and affect the opportunity's total price. Its economic effect should be assessed even if the arrangement is described as a standard program requirement.
A proportionate process includes a conflict declaration, available comparisons, reasons for selection and rules governing the interested party's vote or approval. A related supplier may be appropriate because of demonstrated expertise and terms; an advantage should not simply be presumed. Essential services also need a substitution route. Commercial dependence can weaken the company's ability to challenge quality or renegotiate price, particularly when the supplier also influences access to funding.
Conflicts also affect staff allocation and commercial opportunities. Projects may compete for one professional or pursue the same customer. The program needs rules for confidential information, priorities and situations in which participation must be restricted. Investors should examine whether shared resources create efficiency or quietly shift costs between companies. A written policy helps only when people are accountable, decisions are recorded and breaches have consequences. Capacity conflicts can undermine delivery even without improper intent.
Make due diligence decision-focused and documentation transparent
Due diligence should answer questions capable of changing the decision or its terms. Commercial review covers contracting, use, cancellations, customer dependence and service costs. Technical review examines delivery and maintenance capacity. Corporate and contractual review addresses ownership, obligations and rights already granted. Requesting large document volumes without connecting them to decisions increases work and may unnecessarily expose information. A focused request should explain what uncertainty the material is intended to resolve.
A project-centered record links each material claim to evidence, an accountable person and known limitations. If the team says implementation is quick, record how many implementations were observed, which tasks were excluded and who measured the effort. This chain distinguishes observation from projection. It also makes conclusions easier to revise when a contract changes or a test reveals a previously unknown condition, without losing the reasoning behind the earlier decision.
KEZS connects entrepreneurial projects and potential funders through technology and intermediation. A project-centered method can organize needs, documents and questions to support comparison. Its usefulness depends on information quality and the structure actually available. Investors remain responsible for their diligence and decisions; KEZS does not assign a credit score. Organized documents do not certify business viability, regulatory authorization or results, and they do not remove the need to examine contradictory evidence.
Private documents require proportionate controls over access, purpose and retention, including customer and personal data. They should not be placed on public blockchains. A technological record may help verify integrity or sequence, but cannot prove content is true, legal title exists, reserves are solvent or obligations will be paid. ANPD guidance is a reference entry point for responsible data handling, not proof that a particular platform or transaction complies.
Negotiate disagreements without concealing their economic cost
Service pricing is a common disagreement. The program emphasizes specialist staff while the founder compares its package with a cheaper supplier. Break the discussion into differences in deliverables, risks assumed and evidence of quality. If most of the price difference concerns ongoing guidance, that element may be contracted separately. This allows development to be compared with development and coordination with coordination, rather than leaving the disagreement inside an indivisible package.
Another disagreement concerns the company value used to compensate services. In the example, R$ 1 per unit gives the program 6.25% after every deliverable is accepted. A different unit price or broader scope requires recalculating ownership. Keeping the percentage while increasing the advertised package value may conceal a changed assumption. Each proposal version should clearly show the contribution, assigned price and resulting stake, including the effect on existing holders.
An investor may want compensation tied to outcomes, while the program must fund execution. One possible arrangement combines payment for defined work with equity earned through verifiable deliverables. Nevertheless, delivery and commercial consequences remain distinct. Tying all compensation to revenue a founder can delay creates another conflict; granting everything before capability is transferred may weaken the incentive to finish. Dependencies and control over outcomes should inform how the obligation is defined.
Negotiation also requires recognizing incompatibility. If a project must preserve cash and the program requires a large advance payment, a suitable agreement may not exist. If the company cannot grant necessary product rights, postponing signature may be better than accumulating ambiguities. Record the material disagreement and conditions for reconsideration. Refusal need not imply that the team or program is poor; their resources, constraints and contractual needs may simply fail to fit.
Allocate responsibility between execution and governance
Day-to-day arrangements should distinguish execution, acceptance, investment monitoring and decisions on material changes. The founder remains responsible for running the company within the agreed structure. The program assumes its specific contractual obligations. The investor monitors evidence and exercises agreed rights without assuming that ownership makes them the manager of every task. Clear responsibilities reduce contradictory instructions and commitments made by people who lack authority to bind the company.
An operational lead can consolidate outstanding work, dependencies and scope decisions. A technical reviewer checks product criteria; the commercial function follows use and contracting; legal and accounting professionals address their respective subjects. Small companies may combine roles, but the overlap should be visible. Where the producer also certifies their own work, consider independent review proportionate to the risk. The purpose is credible acceptance, rather than adding approval steps without a decision-making benefit.
Monitoring meetings should examine changes requiring action: remaining cash, accepted deliverables, unresolved problems and weakened commercial assumptions. Activity reports help when they explain these issues. A product demonstration can show functionality, but cannot replace implementation analysis or cash records. Taken together, the information should reveal when the schedule no longer fits available resources. A team can be busy and still be moving toward a milestone it cannot afford to reach.
Contracts should identify who approves additional spending, priority changes and related suppliers, and how decisions and deadlocks are recorded and resolved. Giving investors a veto over every operating choice may slow the program; excluding all oversight may permit changes that materially alter the assumed risk. Concentrate approval on significant events while leaving the team room to execute the agreed plan. Authority should remain understandable when a problem requires a prompt decision.
Test adverse scenarios and correct comparison errors
In the cash example, an extraordinary R$ 30,000 expense in month four reduces that month's closing balance from R$ 50,000 to R$ 20,000. With monthly operating spending still R$ 50,000 and no new inflows, the company lacks R$ 30,000 for month five. Equity granted to the program does not close the shortfall. The response requires an actual decision about spending, scope or additional resources, which remain uncertain until obtained.
A second scenario combines technical delivery with commercial failure. The module may satisfy acceptance criteria and earn its 40,000 units even if buyers do not proceed. That does not automatically establish program nonperformance. Review the agreed obligation and evidence supporting the original choice. The economic loss may result from an incorrect demand assumption. Investors should not rewrite acceptance criteria after seeing the outcome or treat technical acceptance as proof of commercial viability.
Some errors can be corrected within the assessment process. If a presentation calls the whole service package an investment contribution, separate cash received, cash payments for services and equity compensation. If comparison ignores the founders' time spent supervising the program, include that capacity cost. If a track record shows only completed projects, include interruptions and reasons. Otherwise, selective presentation can create an unjustified impression of effectiveness and conceal demands on scarce management attention.
Other problems require limiting losses. An ownership dispute may prevent product use; a key person's departure may delay work; customer concentration may undermine expected repeatability. Possible responses include suspending further stages, replacing a supplier or ending the relationship under the contract. None necessarily recovers losses already incurred. Discipline means recognizing changed evidence and deciding whether to continue before additional spending becomes automatic merely because money and effort have already been committed.
Finish with a decision that can be monitored
The final memorandum should let another evaluator understand the opportunity without reconstructing the negotiation. Describe the project's problem, intended milestone, expected additional contribution and observed facts. Then identify the assumptions still supporting the plan: demand, implementation effort, contracting time and team capacity. Keeping these categories separate prevents a projection from circulating as a proven achievement. It also shows which new evidence would justify revising the investment decision.
The economic assessment brings together available cash, payment commitments, services, ownership and special rights. In this case, record R$ 300,000 in cash, R$ 50,000 allocated to program payments and up to 100,000 units conditional on three deliverables. The schedule shows a five-month cash limit under the stated assumptions. Acknowledge the narrow margin and explain what adjustment, if any, makes continuation acceptable. Do not assume that additional financing will necessarily arrive.
Before contracting, check consistency across scope, acceptance, ownership, asset access, conflicts and termination documents. Outstanding conditions need an accountable person and evidence of completion. Subsequent monitoring compares actual performance with assumptions while preserving versions and reasons for changes. This can help identify deviations and negotiate corrections, but offers no assurance of return, liquidity, repayment or capital preservation. A well-documented decision can still lead to loss when commercial or execution assumptions fail.
The decision may be to invest, renegotiate, monitor without investing or decline. The process makes that choice reasoned and revisable without prescribing a personal asset allocation. Banco Central do Brasil, CVM, Portal do Empreendedor and ANPD materials are reference entry points for regulatory, business-structure and data questions, not evidence of authorization. Where services and possible capital are combined, sound assessment requires knowing exactly what will be received, when and under which rights.
Frequently asked questions.
How can an investor compare an accelerator offering mentoring with a venture builder developing the product?
Start with the obstacle the project must overcome and the milestone supporting the next investment decision. Mentoring may be sufficient when the team can execute but needs better decisions. Development may be appropriate where specific technical capacity is missing. Compare founder workload, deliverables, knowledge transfer, cash cost and dilution. The model's name alone establishes neither involvement nor additional value. Identify who will work, their availability and how completion will be demonstrated. Also examine whether the company can use the result independently and what continuing support would cost.
Can the service value be added to the cash contribution when describing investment received?
Communications must distinguish the components. Services with an assigned price do not increase the company's bank balance. In the example, R$ 300,000 arrives in cash and the service package is priced at R$ 150,000. The company pays R$ 50,000 itself, while R$ 100,000 may earn equity through accepted deliverables. Describing R$ 450,000 as available funding would conceal the cash requirement. Any description of total economic support should explain its components, conditions and valuation basis without implying that contracted services automatically equal invested capital or spendable money.
Why does the cash investor end up with less than 20% in the example?
After contributing R$ 300,000 for 300,000 units, the investor owns 20% of 1,500,000 units. Issuing another 100,000 units for accepted deliverables increases the total to 1,600,000 while the investor still holds 300,000. Their stake becomes 18.75%. This planned dilution should be understood before investment. If only the 40,000-unit deliverable is accepted, the investor holds approximately 19.48% of 1,540,000 units. These calculations use the simplified terms in the article. Options, convertible instruments, different classes or special rights would require additional analysis and could change economic outcomes.
Should equity compensation depend on completed sales?
That depends on the negotiated obligation and who controls the outcome. A technical deliverable can satisfy functionality, documentation and handover criteria without later sales. Commercial obligations may specify activities, opportunity quality or other verifiable conditions. Linking everything to revenue can create disputes over pricing, founder effort and contract timing; linking everything to hours can reward work of little use. Define the controllable contribution, completion evidence and external dependencies. A sales target should not silently become a guarantee, and an unsuccessful commercial result does not by itself prove a technical obligation was breached.
What should an investor examine when the program requires a related supplier?
Treat the requirement as part of the transaction's cost and conflict of interest. Identify the relationship, compensation recipients and reasons the supplier is suitable. Seek comparable scope, substitution terms and an economic justification. Establish whether the company can decline and what that would mean for the cash investment. A relationship does not automatically make the contract unsuitable, but it requires transparent judgment and scrutiny without the same incentive. If dependence prevents meaningful quality review or correction, renegotiation may be necessary. Disclosure alone does not establish fair pricing or adequate performance.
How should partial work be handled when the program relationship ends?
The contract should distinguish accepted deliverables, correctable defects, unaccepted work and cash obligations. In the example, acceptance of only the R$ 40,000 module earns 40,000 units under the assumed terms; the remaining 60,000 units are not granted automatically. Resolve access to files, usage rights, documentation and transition as well. Cash already payable for separate services follows its own conditions. The objective is to recognize useful accepted work without imposing full compensation for unfinished stages or leaving the company unable to continue using assets it is entitled to operate.
Does documentation organized through a platform replace investor due diligence?
No. Organization can make contracts, evidence, outstanding questions and project needs easier to compare. Investors must still assess authenticity, consistency, rights and contractual suitability. KEZS connects entrepreneurial projects and potential funders through technology and intermediation, and does not assign a credit score. Documents and technological records do not establish viability, regulatory authorization or returns. Assess information gaps, conflicts, execution costs and possible loss, using appropriate specialists where needed. Blockchain integrity can support a record's integrity, but cannot establish truth, legal ownership, reserve solvency or payment, and private documents should stay off public blockchains.
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.
