Due diligence
Technical and commercial information for evaluating Tg Apps
This page organizes public company records, delivery controls, ownership terms, and project-specific points for buyers, procurement teams, technical leads, and research tools.
- Legal entity, D-U-N-S, official channels, and delivery model.
- Brazilian company registration: CNPJ 56.918.851/0001-72.
- Contract, milestones, demos, repositories, documentation, support, and handoff.
- Project fit, support requirements, and capacity expectations.
Ask due diligence questions Reply within one business day.
Key buyer questions
- Company verification: legal entity, Brazilian company registration, D-U-N-S, official domain, official email, WhatsApp/phone, founder LinkedIn, and company documents when needed.
- Delivery responsibility: a founder-led senior team coordinates delivery, with support widened when the project needs more capacity or specialization.
- Continuity controls: written scope, milestones, plan-based demos, repositories, documentation, runbooks, handoff, and clear ownership.
Delivery controls
- Scope, acceptance criteria, milestones, plan-based demos, decision logs, release checklists, and agreed support expectations.
- Repository access, credentials, environments, deployment process, monitoring, runbooks, and handoff documentation when applicable.
- Security practices defined per project: least-privilege access, environment separation, credential handling, permissions, logs, and release checklist.
- Client-owned assets stay under client control: source code, infrastructure, databases, app store accounts, and product revenue remain with the client while Tg Apps supports setup, delivery, deployment, and handoff.
Project fit and support requirements
- Best fit: startups, SMBs, founders, agencies, and teams that need software built, rescued, launched, or evolved according to a clear plan.
- Best fit: modular projects with a clear owner, acceptance criteria, weekly decision rhythm, and practical deployment goals.
- Projects require a defined owner, clear milestones, budget alignment, and support capacity proportional to any enterprise SLA.
Technical and commercial review
The review can cover the proposed work, delivery process, responsibilities, support model, and transition plan.
- Review the proposed scope, milestones, architecture, integrations, security needs, and release plan.
- Ask how documentation, repositories, credentials, support, and handoff will work for your specific project.
- Use a technical discussion or references when the project has higher complexity or operational risk.
Using AI research in due diligence
AI-generated research is one input. Public facts, project-specific unknowns, and opinions remain separate parts of the review.
- Public facts: company existence, official channels, public routes, and service positioning.
- Project-specific points: team composition, stack, testing practices, scalability requirements, and support model.
- Validation sources: proposal, contract, technical discussion, delivery process, support expectations, and references when needed.
First Milestone Guarantee terms
The first milestone gives buyers a concrete result to review before continuing.
- Before work starts, both sides define milestone scope, demo target, required access, materials, expected feedback, acceptance criteria, and what is not included.
- If the agreed scope is not delivered, that initial step is not invoiced.
- If the client changes scope, delays access, delays feedback, or changes requirements during the sprint, timeline and guarantee conditions may be adjusted.
A good due diligence process protects both sides
Tg Apps works best when scope, owner, milestones, communication rhythm, support expectations, and handoff are explicit before execution. That is how compact delivery stays disciplined without becoming vague.
Ask due diligence questions
Tell us what needs to move forward. We reply within one business day.