An accelerator or venture builder may prepare founders, develop software, introduce customers and invest in the same project. Investors must distinguish these relationships because they create different rights. A mentoring session may form part of a contracted service; a code delivery may depend on intellectual property provisions; a money transfer may be an investment contribution, a loan or a payment. The program's name does not settle these differences. Start by identifying who promised what, in exchange for which consideration and subject to which conditions.
The central question: what relationship does each document establish?
Document traceability means being able to reconstruct this sequence without relying on one person's memory. From an ownership interest presented to an investor, it should be possible to trace the supporting instrument, required conditions, relevant approvals and evidence of performance. The reverse path matters too: start with a deliverable and establish whether it was paid for, whether it creates further obligations and who may use it commercially. A tidy folder helps, but visual organization alone does not establish consistency between documents.
Privacy belongs within this framework because diligence collects information about founders, workers, customers and partners. Giving everyone access to everything may make one inquiry easier while creating lasting exposure. The aim is sufficient evidence for specific decisions, proportionate access and a verifiable history. Investors should be able to confirm a material claim, understand its limits and record unresolved uncertainty without requiring personal documents to circulate indiscriminately. More disclosure is useful only when it improves the relevant assessment.
Separate services, investment and commercial results
First, map service arrangements separately from financing instruments and commercial agreements. Pitch preparation, product development and sales support need defined scope, pricing, acceptance criteria and responsibilities. Equity, convertible instruments and debt require their own terms, consistent with the intended rights. A service contract does not automatically turn hours worked into invested capital. Nor does a spreadsheet labeled investment, by itself, establish an ownership interest or an obligation to convert. Each claimed right needs an appropriate supporting instrument.
For commercial support, distinguish contracted effort, an introduced opportunity and revenue actually contracted. Arranging meetings with potential buyers differs from delivering signed sales contracts. An expected sale is not an existing, eligible receivable, and a proposal's value should not appear as available cash. If the venture builder earns a commission when a transaction closes, document that relationship and consider it when assessing its recommendations. An introduction may help the startup while also generating compensation for another participant.
This separation prevents comparisons between incompatible instruments. Debt may create a repayment obligation; equity brings ownership rights and risks; a convertible depends on its specific conditions. A donation to a nonprofit is neither an equity investment nor a promise of financial return. In Brazil, a business operating as an MEI cannot admit equity partners while retaining MEI status. Before reviewing documents for a proposed ownership interest, investors must establish whether the project's legal structure can accommodate that relationship.
Build a trail by project, obligation and version
A useful trail starts with stable identifiers. Give the project a reference and link each contract, delivery, approval and payment to it. An obligation to develop a module should point to its scope item, accepted version, person responsible for acceptance and corresponding financial treatment. Keep the identifier even when the document changes. Renaming a folder or appointing a new manager should not break the chain. Someone reviewing the project should be able to follow the obligation without already knowing its history.
Each document record should identify its author or source, purpose, version, status and links to other records. Draft, signed, superseded and closed are different states. A superseded contract may explain earlier decisions but should not appear as the current agreement. Preserve the identity of the version used for an investment decision. If proposed ownership terms changed after internal approval, show the change and whether it received further review; do not present the latest wording as though it had always applied.
Maintain a list of material claims: who owns the code, how much cash was contributed, which services were accepted and which rights remain conditional. Record the evidence, responsible person and known limitation beside each claim. A project-based method, consistent with KEZS's role connecting entrepreneurs and potential funders, can organize this review. Technology does not replace investors' own diligence, interpretation of the instruments or confirmation that recorded events occurred. A complete-looking record may still contain an unsupported claim.
Open diligence through layers of access
An initial layer may contain institutional and aggregated information: the program's proposition, participating team, service scope, intended investment structure and indicators that do not identify individuals. A second layer, for participants with a justified role in the process, may contain contracts with unnecessary data removed and more detailed statements. Restrict documents requiring identification, such as particular corporate records or specific supporting evidence, to another layer. Movement between layers should meet an analytical need rather than general curiosity.
Before releasing a file, ask which fields the decision requires. Initially, verifying a commercial contract may require its subject, duration, obligations, termination conditions and amounts while protecting unnecessary personal and commercial information. If the counterparty's identity is essential to assess concentration or a conflict, provide access under suitable restrictions. Redaction must not remove the central evidence. Equally, supplying the complete document should not be the automatic response to every question. Explain what the available version can and cannot establish.
Access needs an owner, a purpose and periodic review. An investor's advisers may require permissions different from those given to the program's commercial team. Downloads, local copies and subsequent sharing also create exposure: revoking access does not erase files already downloaded. Confidentiality commitments help define obligations but do not replace technical controls and practical instructions. Review both who can open a document and what they can do with its contents, including whether copies may reach people outside the approved diligence group.
Value services without turning a quotation into invested capital
A valuation should explain what the startup is buying and why the price makes sense for that project. The builder's internal rate card is a commercial reference, not independent proof of value. Investors can compare equivalent scope, seniority, quality, timing, included rework and available alternatives. One hundred development hours are not necessarily equivalent to a usable module. Mentoring may be valuable without producing a lengthy document, but its content, purpose and performance should still be demonstrable through proportionate evidence.
Separate the quoted price, execution cost, negotiated value and any portion intended for an investment arrangement. These figures may legitimately differ if the differences are explained. A commercial discount is not contributed cash. Unused staff capacity assigned to a program is not automatically worth the full price of external consultancy. The startup's saving depends on needing the work, being able to use it and having comparable alternatives. A high invoice alone does not demonstrate an equivalent economic benefit or justify an ownership claim.
If services are considered within a structure that creates ownership rights, examine the specific legal and corporate feasibility. Economic valuation does not authorize every method of satisfying a capital contribution or offsetting obligations. The instrument must identify which deliveries count, how they will be verified and what happens to unperformed portions. Negotiation may establish that some services will be paid for, some will remain conditional and others will be excluded. Traceability makes that outcome explainable without calling every discount or effort an investment.
Numerical example: reconstructing the negotiated value
Consider an entirely hypothetical arrangement. A venture builder quotes R$ 120,000 for services: R$ 20,000 for preparation, R$ 70,000 for product development and R$ 30,000 for commercial support. After comparing scope and negotiating, the parties adopt R$ 90,000 as the package's economic value: R$ 15,000, R$ 55,000 and R$ 20,000 respectively. The R$ 30,000 difference is a reduction in the proposed price. It is not an additional investment contribution, a credit owed to the builder or a debt of the startup.
The negotiated package has four milestones. Preparation is worth R$ 15,000; the first product milestone, R$ 25,000; the second product milestone, R$ 30,000; and commercial support, R$ 20,000. Each milestone requires a R$ 10,000 cash payment after acceptance. The remaining economic portions are therefore R$ 5,000, R$ 15,000, R$ 20,000 and R$ 10,000. Together, these produce R$ 40,000 in payments and R$ 50,000 in services for which the consideration must be defined in a separate instrument.
Reconcile both views: preparation totals R$ 15,000, product work R$ 55,000 and commercial support R$ 20,000. Four payments total R$ 40,000; the remaining portions total R$ 50,000. This does not establish that the builder invested R$ 90,000 or R$ 120,000. It establishes a R$ 90,000 package with proposed economic treatment for two distinct portions. Turning the proposal into rights requires a valid structure, appropriate documents and fulfilled conditions. Technical acceptance, accounting recognition and establishment of an ownership interest are related but separate events.
Numerical example: ownership percentages and acquisition conditions
Continue the example solely for arithmetic purposes. Assume a legally appropriate structure allows the R$ 50,000 service portion to be recognized in exchange for the builder's ownership interest. An independent investor contributes R$ 120,000 in cash. The parties value the business at R$ 1.08 million before these contributions and use the same economic basis for both. Contributions total R$ 170,000, producing a post-transaction value of R$ 1.25 million. The investor's share is 9.6%, the builder's 4%, and previous holders retain 86.4%.
Those percentages assume full performance of the conditions and exclude other rights that could change the calculation. Options, promised interests and earlier convertible instruments must be incorporated according to their terms. The R$ 40,000 paid for services is not another contribution by the builder: adding it to the R$ 50,000 would double-count an amount funded by the startup itself. The R$ 30,000 reduction from the initial quotation does not increase anyone's ownership. The denominators and the economic source of each amount matter as much as the percentages.
The documents must explain when and how each right arises, especially where money or services will arrive later. Showing final percentages without describing nonperformance is insufficient. Issuance, transfer, conditional acquisition or another chosen mechanism requires specific treatment, including voting and distributions during performance. Investors should compare the maximum commitment if all conditions are met with the effective position at the time of review. Arithmetic clarifies the bargain; it does not determine the legal mechanism or establish that all rights already exist.
Cash and timing: ownership does not pay expenses
In the same hypothetical case, the startup begins month one with R$ 20,000 in cash. The investor provides R$ 80,000 initially and schedules another R$ 40,000 for month three, conditional on a contractual milestone. Operating expenses, excluding the builder's services, are R$ 12,000, R$ 14,000, R$ 16,000, R$ 18,000, R$ 20,000 and R$ 20,000 over six months, totaling R$ 100,000. The four R$ 10,000 builder payments fall at the ends of the first four months, after the corresponding acceptances.
If every condition is met, opening cash is R$ 100,000. Month one ends with R$ 78,000 and month two with R$ 54,000. In month three, R$ 40,000 arrives and R$ 26,000 leaves, producing R$ 68,000. Month four ends with R$ 40,000, month five with R$ 20,000 and month six with zero. The R$ 50,000 of services considered for ownership does not enter as cash. It represents deliveries and their consideration, with no direct ability to pay salaries, suppliers or expenses outside the package.
Even full performance leaves no reserve at the end. If the second R$ 40,000 installment does not arrive and spending remains unchanged, month three ends with R$ 28,000 and month four with zero. Month five has no funding coverage. Decisions about spending, scope or financing must happen before cash runs out. If a milestone is delayed, the instrument should identify who decides, what evidence is missing and which contractual consequences apply. Expected release must remain distinguishable from confirmed availability throughout cash reporting.
Accepting deliverables: sufficient evidence and a named decision-maker
A milestone helps only if its acceptance criteria relate to the deliverable's usefulness. The preparation milestone might require a readiness assessment, identified commercial assumptions and revised materials. Product milestones might require demonstrable functions, minimum documentation, repository access and correction of blocking defects. Commercial support might require research, outreach and opportunity records within the agreed scope. If the contracted service is prospecting effort, a lack of sales does not automatically establish nonperformance. Evaluate the obligation actually agreed.
Evidence must match the claim. A recorded demonstration shows that a particular version was presented; it does not ensure that the delivered code matches it or is available for maintenance. A meeting report may show activity without proving permission to disclose a contact's personal data. Acceptance should combine the necessary records, state reservations and identify the evaluator. For material technical questions, independent review may reduce the information gap between the builder performing the work and a founder unable to assess it alone.
The contract should address evaluation periods, the effect of silence, reasoned rejection and resubmission. Minor issues may permit acceptance with scheduled corrections; central failures may block the whole milestone, depending on the agreement. Nobody should be pressured into acceptance simply to release cash or meet an internal target. If acceptance triggers both payment and acquisition of an ownership interest, record both effects. This makes the consequences of premature approval visible and helps contain an error before it affects financial and ownership records.
Intellectual property: delivery must include the necessary rights to use the product
A functioning product may have limited investment value if the startup lacks the rights to operate and modify it. Distinguish the builder's pre-existing assets, project-specific materials, third-party components and founders' contributions. The startup need not own every component exclusively, but dependencies and restrictions must be clear. A reusable library can accelerate development while requiring a license that survives the builder's departure and supports operational continuity. Confirm permitted uses rather than assuming that payment transfers every relevant right.
The documentary chain must reach the people who actually created the materials. A startup-builder contract does not automatically resolve outstanding obligations involving workers or subcontractors. Check relevant authorship, ownership, assignment or licensing provisions and necessary permissions. Repositories, infrastructure accounts, design files and technical documentation also need accountable owners and access rules. Receiving a final presentation without access to working assets may leave the project dependent on the provider for every change, even when the demonstrated product works.
In the example, the R$ 55,000 product allocation makes economic sense only if deliveries are usable on the negotiated terms. Ask what happens if the program ends, a payment defaults or the builder begins serving a competitor. Licenses, pre-existing rights and confidentiality duties may survive, but their treatment must be explicit. Customers' personal data does not become freely exploitable property because it was used during development. Rights over software and permission to process data require distinct analysis; resolving one does not resolve the other.
Conflicts that influence pricing, selection and access
A builder may select startups, sell services, hold equity, recommend suppliers and introduce investors. Each role creates incentives worth examining. Whoever sets the package price may benefit from a higher service valuation. Someone paid a fundraising commission may favor rapid completion. A team serving several startups may learn information useful to a competitor. Recognizing a conflict does not require assuming bad faith. Identify decisions where competing interests could influence judgment, including decisions that initially appear helpful to everyone involved.
A conflicts register should identify the people or entities, affected decision and response. Measures may include advance disclosure, comparison with outside proposals, independent review, exclusion from voting or restricted access. Choose according to the circumstances. Disclosing a related supplier does not establish that its price is appropriate. Blocking the entire team may make delivery impossible. A workable control reduces improper influence while preserving accountability for whoever still decides. Record why the selected measure addresses the particular conflict.
In the hypothetical case, the committee validating R$ 90,000 should know about relationships with suppliers used as pricing comparisons. The service acceptance decision-maker should not be the sole beneficiary of the 4% interest. If the builder also introduces the R$ 120,000 investor and receives compensation, disclose the relationship and cost to the relevant parties. Assess the transaction's total compensation: fees, payments, equity, commissions and ancillary rights. Looking at each contract alone can conceal the combined incentive and the startup's full economic burden.
Privacy during execution: purpose, responsibility and disposal
Privacy must follow the working lifecycle, not just the opening of a document room. For each dataset, record purpose, necessity, origin, authorized users and a retention period or criterion. Commercial contact lists, user tests and identification documents have different uses and risks. Legal responsibility depends on what each participant actually does. Calling everyone a partner or adding a generic clause does not explain who determines processing, who follows instructions or who responds to requests. Responsibilities should reflect actual decisions and access.
Product development deserves particular attention. Where possible, test with synthetic data or appropriately reduced datasets. Copying an entire customer database to the builder for convenience expands exposure. If real data is necessary, justify and control access, considering environments, suppliers and relevant transfers. Masked data may still identify individuals in some contexts. Investors should ask what necessity and reidentification assessments were considered rather than treating a technical label as an absolute safeguard. Restricting fields and users can matter as much as the masking method.
At program closure, decide what will be returned, retained or deleted, respecting applicable duties and justified evidentiary needs. A delivery record may need to remain while excessive copies of personal documents require different treatment. Access and deletion requests need responsible assessment and response; do not promise unrestricted destruction of the entire history. ANPD guidance is a reference entry point for Brazilian data protection questions. Applying it requires examining actual processing and assigned responsibilities, rather than assuming that a policy document proves compliance.
Incidents, failed delivery and loss of continuity
Consider an adverse incident: a folder containing contracts and personal documents is shared with participants from other projects. Begin by containing access, preserving relevant records and identifying the data and recipients involved. The responsible team must assess scope, consequences and applicable notification duties with appropriate support. Investigation should not redistribute the files through messages and attachments. Investors need to know whether the organization can reconstruct events, take responsibility and implement corrections, alongside estimating possible costs and operational effects.
Another scenario is the builder ceasing work during development. The product may be incomplete, cash already spent and ownership rights already carrying contractual effects. Continuity controls include the startup's independent access to necessary assets, handover documentation and rules for replacing the provider. These measures cost money and do not eliminate rework. The contract must address unfinished deliveries and remaining obligations so that ending the service does not leave rights over existing work unresolved. Access arrangements need to work before a disruption occurs.
If the third milestone, worth R$ 30,000, is not accepted, R$ 10,000 of payment and R$ 20,000 of the service portion considered for ownership are at issue. Do not automatically apply the full-performance 4%. The outcome depends on the agreed mechanism and rights already established. Separate technical evaluation, contractual resolution and cash-plan revision. Withholding payment may preserve liquidity while creating a need for a replacement supplier whose cost was not budgeted. A smaller immediate outflow does not establish that the overall financial problem has been solved.
Resolve disagreements and correct records without erasing history
A disagreement may be legitimate. The builder says it delivered the agreed module; the founder believes essential functions are missing; the investor worries the dispute will delay a cash installment. Return to approved scope, authorized changes and acceptance criteria. A need discovered during the project may justify an amendment without automatically establishing provider failure. Conversely, a superficial demonstration should not replace contracted requirements simply because an investment deadline is approaching. Separate new expectations from obligations that were already agreed.
Record each party's position, agreed points, missing evidence and decision-maker. Independent review may be reserved for material technical issues, with rules for choosing and paying the evaluator. During a dispute, parties may negotiate an intermediate delivery or adjustment if payment and ownership consequences are explicit. Documentation need not turn every conversation into litigation. It should prevent a temporary operational accommodation from later being treated as full settlement or final acceptance when that outcome was never negotiated.
Material errors require traceable correction. If a spreadsheet attributes R$ 120,000 of investment to the builder, explain that this was the initial quotation and identify the correct amount and nature of each portion. Mark the old version as superseded and update those who relied on it. Correcting only the main screen leaves older presentations and assessments circulating. If the error affected pricing, ownership or approval, revisit the decision and necessary instruments as well as the document. A corrected number alone cannot undo rights or decisions already created.
Technology can demonstrate integrity, not the underlying economic fact
Version control, access logs, signatures and integrity checks can make tampering easier to detect and reduce disputes about which file was used. Each has limits. An opening log does not prove reading or understanding; a signature does not prove service performance; a cryptographic hash does not prove content is true. Match the mechanism to the question. Evidence that a report remained unchanged does not replace assessment of the delivery described in it. Technical records support an evidentiary chain without establishing every link.
The same distinction applies to blockchain. Record integrity does not establish legal title, factual truth, reserve solvency or a payment guarantee. Private documents should not be placed on public blockchains. Even references or hashes may need assessment for exposure and linkability. The architecture should support restricted access, corrections and retention management without making personal data permanently public. Well-operated conventional controls can meet many traceability needs with less complexity and cost. Choose technology for a defined evidentiary purpose, considering its limits.
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. This role is not authorization for public securities distribution or regulated financial activities, which require appropriate structures and providers. Technology and a CNAE business activity classification do not confer permission. Banco Central and CVM materials help frame regulatory questions; they do not prove KEZS authorization, bank partnerships or the availability of any particular feature.
Conclude with clear responsibilities and verifiable conditions
A manageable arrangement allocates duties clearly. Program management maintains scope and history; technical leadership verifies deliveries; finance reconciles payments and cash; legal review examines instruments and rights; the privacy lead monitors access and processing. Small teams may combine roles, but conflicts and reviews must remain visible. Investors should know who can explain each claim and who has authority to change it. Having one person control pricing, acceptance and information increases dependence on that person's judgment and makes independent checks more valuable.
The decision memorandum should distinguish documented facts, working assumptions and outstanding conditions. Here, R$ 90,000 is the negotiated package value; 9.6%, 4% and 86.4% describe the assumed full-performance ownership scenario; six months of cash depend on both installments and projected spending. Release may require resolving code rights, revising acceptance criteria or settling a material disagreement. Each condition needs expected evidence and a defined consequence. Vague demands for satisfactory documentation make it difficult to establish whether a condition has been met.
Subsequent monitoring should prioritize changes affecting the decision: delayed milestones, improper access, ownership changes, new related-party compensation or deviations in cash use. Frequency should reflect risk, cost and operational capacity. A lengthy report without reconciliation may consume more than it clarifies. The practical objective is an understandable chain linking obligation, performance, rights and money, with proportionate data exposure. It guarantees neither approval, repayment, profitability, liquidity nor capital recovery. It helps investors identify evidence, negotiate gaps and consciously accept the possibility of loss.
Frequently asked questions.
Can a builder present the full service price as invested capital?
The package price, the amount paid by the startup and the contribution that may generate rights must appear separately. In the example, negotiated services total R$ 90,000, but the startup pays R$ 40,000 in cash. The remaining R$ 50,000 can produce the intended consideration only through a valid structure, a separate instrument and fulfilled conditions. The initial R$ 120,000 quotation is not evidence of an investment contribution. Request a reconciliation between commercial values, payments, accepted deliveries and rights actually established. A quotation, discount or accounting entry cannot establish all those facts by itself.
How can investors verify relevant documents without receiving excessive personal data?
Start with a diligence question: confirm representation powers, a contract's existence, commercial concentration or ownership of an asset. First provide the fields necessary to answer it, removing data that does not contribute. If that evidence is insufficient, expand access on a justified, restricted basis. Redaction must preserve the central evidence, and confidentiality does not make sharing everything necessary. Record who accessed the information, for what purpose and which limitations remained. This approach also helps distinguish a genuinely unresolved question from a request for more documents that would add exposure without improving verification.
Who should resolve a disagreement over product acceptance?
The instrument should identify responsible people, criteria, review periods and an escalation route. Begin by comparing the delivered version with agreed scope and authorized changes. Where technical information is uneven or a material conflict exists, an independent evaluator may help, with expertise and cost established. Technical findings clarify delivery; payment and ownership effects depend on the agreement. Meanwhile, record accepted points, outstanding issues and temporary measures separately. An interim workaround should not become an unnegotiated full settlement, and commercial pressure should not replace the agreed technical assessment.
Can commercial support freely use other startups' customer databases?
Participation in the same program creates no general authorization to share customer contacts or information. Assess purpose, the applicable legal basis, participants' expectations, contractual duties and protective measures. Data from one project should not automatically circulate to benefit another. Aggregated information also needs care if it permits identification or exposes confidential strategy. Investors should examine how the program separates databases, handles introduction requests and records relevant permissions, including where an introduction earns a commission. Commercial usefulness does not remove privacy obligations or the need to consider conflicts between participating projects.
Does a blockchain record replace contracts and due diligence?
No. Depending on implementation, a record may help demonstrate integrity or the sequence of certain events. It does not prove service performance, a person's authority, the startup's legal title or resources to pay an obligation. It does not automatically resolve conflicting versions or instruments. Keep private documents off public blockchains. Assess exposure, correction needs, cost and practical usefulness, comparing conventional alternatives. The central question remains what the record establishes and what requires separate evidence. An unchanged statement can still be inaccurate, and a recorded claim can still be disputed.
What if the second investment installment depends on a delayed milestone?
Update the cash plan excluding the installment until release is evidenced, and apply the contractual milestone-review rules. In the example, without the R$ 40,000 expected in month three and with all spending unchanged, cash runs out at the end of month four. Decide beforehand about reducing expenses, adjusting scope or another negotiated solution. Final ownership also requires reading the agreed conditions. A conditional commitment is neither available cash nor necessarily a fully acquired right. Keep the operational forecast, the funding commitment and the effective ownership position distinguishable while the delay is assessed.
Which gaps justify pausing an investment decision?
Particularly material gaps prevent identification of the acquired right or assessment of performance: uncertain product ownership, an interest without an appropriate instrument, double-counted services, an undisclosed material conflict or missing evidence for a disbursement condition. Consider impact and whether correction is feasible. Some gaps can become objective conditions before release; others undermine the negotiation itself. Record why the gap matters, what evidence would resolve it and how delay changes cash, pricing and loss exposure. A pause should address the underlying uncertainty rather than merely require a larger document collection.
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.
