Frequently asked questions.

No. You do not need to write code. You should deeply understand the problem, have observed it up close, or have meaningful access to the people who experience it every day. We look for domain knowledge, customer empathy, and active commitment—we provide the full product strategy, design, and engineering team.

No. We review every application for problem severity, customer pain, current workarounds, founder contribution, and technical feasibility. We only partner on ventures where there is compelling evidence that a focused software product can solve a genuine, repeated pain point.

50/50 is TBLLAB' proposed standard starting point for accepted co-build partnerships. The actual arrangement is documented in a signed agreement before development begins and accounts for specific responsibilities, pre-existing IP, ongoing time commitments, vesting schedules, dilution protections, and governance.

No. The application is solely an initial expression of interest. A binding partnership exists only after both sides have completed exploratory due diligence, aligned on terms, and executed formal written agreements.

IP ownership and licensing rights are established in the written agreement before substantive engineering begins. Typically, IP created for the venture belongs to the new venture entity, with appropriate protections for pre-existing founder knowledge and studio foundations.

Do not assume cash investment is included. TBLLAB primarily contributes high-tier product strategy, UI/UX design, and full-stack engineering execution. Direct cash costs (such as 3rd-party hosting, paid APIs, incorporation, or marketing ad spend) are discussed and allocated transparently in the co-build agreement.

We focus on shipping the smallest useful product. Typically, discovery and validation take 2-3 weeks, followed by a 4-8 week focused build cycle to get a live, usable product into the hands of initial test users. We iterate rapidly based on real usage rather than theoretical roadmaps.

TBLLAB shares operational and technical infrastructure where practical to move quickly. However, whether a venture requires a separate legal incorporation, bank account, commercial contracts, tax registrations, or regulated licenses depends on its jurisdiction, liability profile, and business model. We evaluate this with qualified legal and accounting counsel rather than promising a single blanket structure.

You can mention this in your application. Whether an NDA is appropriate and can be executed is evaluated before sensitive or proprietary information is exchanged. We strongly advise that you do not include trade secrets or confidential data in the initial application form.

The signed agreement clearly outlines pause, wind-down, and exit mechanisms. It defines how incurred expenses are handled, who retains which code assets and access rights, and how equity or intellectual property obligations are resolved.