We build with trust
and full transparency.

Why not build this on your own

• Why not just build this on your own?

  Now building is easy. Making something that monetizes and scales isn't. Most solo founders can build a product — what usually breaks is everything around it: finding the right idea, assembling a strong team, getting distribution right, turning early traction into real revenue, and sustaining execution over time. These are not execution problems, they are coordination and system problems. Junyo exists to solve exactly that. You start from a validated opportunity, you join a team designed to win, you operate inside a system that removes friction. You still build — you just don't build alone.

Role & commitment

• What does it mean to be a founder in Junyo?

  You are not a contributor. You are a founder within a small team building a real company. You operate fractionally, but with full ownership, accountability and responsibility.

• How much time do I need to commit?

  Each project is built for fractional contribution, not casual participation. You are not expected to work full-time, but you are expected to operate at a founder level. Commitment is defined by impact, not hours. This is not asynchronous or isolated work — you coordinate with your team regularly, attend syncs and joint decision-making, and stay responsive when the team needs to move. You don't commit fixed hours. You commit to the team and to making the company work.

• What happens if I leave the project?

  Two things happen. First, the platform (Residents) will actively replace the role to keep the team moving — continuity of the company comes first. Second, ownership is protected by a 1-year cliff: if you leave before 12 months, you forfeit all ownership (no equity, no profit share); after the cliff, ownership reflects your validated contribution over time. This ensures commitment is real and that ownership stays aligned with long-term builders.

• Can I work on multiple projects?

  Yes. Many contributors participate across multiple ventures over time. This allows you to build a portfolio of ownership across companies.

• Can I work on Junyo projects without making it public?

  Yes. You can participate in a venture without publicly disclosing it. Your work can remain visible only to the team, there is no requirement to announce your participation, and your current employer does not need to be aware. Designed for experienced operators who want to build without creating unnecessary exposure. You can stay private externally — but internally, you operate as a fully committed founder.

• What profiles are you looking for?

  Senior operators who are highly skilled in a specific domain, know how to leverage AI to increase output, and are comfortable taking ownership.

Ownership & economics

• How do I make money?

  Two sources of upside: equity (long-term ownership) and profit sharing (annual cash distribution). Many projects monetize early, so returns can start within the first year. Some ventures are designed to generate revenue within weeks, allowing contributors to participate in profit distribution early.

• How does ownership work?

  Ownership is not fixed upfront — it evolves based on contribution. Allocated at defined stages (gates), based on real impact, and adjusts over time. Ownership doesn't dilute arbitrarily, it evolves based on real contribution over time.

• What kind of ownership do I receive?

  During the build phase: phantom equity (dynamic, flexible) that converts into real equity at spin-out.

• What is profit sharing?

  Annual distribution based on net profit, mirroring real business performance. Build stage: no revenue yet. Validation stage: first revenues appear. Growth stage: profit distribution becomes meaningful.

• Will I get diluted?

  Not by default. New contributors are only added with equity when revenue does not justify hiring. Most growth-stage roles are hired using cash once the business generates revenue. Projects are designed to avoid dependence on venture capital — one of the main sources of dilution in traditional startups. Dilution is a decision, not a mechanism: it happens only when it improves the company, decided by existing owners (Residents + Fractional founders). In many cases, early contributors maintain strong ownership as the company grows.

Projects & companies

• What kind of companies does Junyo build?

  Digital businesses (no heavy physical infrastructure). B2B, B2C or B2B2C models, typically highly verticalized (focused problems, clear niches). Medium product complexity — enough to create defensibility, without long build cycles. Non capital-intensive go-to-market, built in weeks not years, designed for early monetization, focused on real business models that don't depend on venture capital. Designed to reach breakeven quickly and grow sustainably. Not experiments — real companies with clear economics.

• When is a company actually created?

  Only when the project proves it works. No legal setup upfront, no need to create a company early. Formalization happens at traction.

• What happens if a project succeeds?

  It spins out into an independent company. Ownership converts into equity or liquidity.

Platform & support

• What do Residents actually do?

  Residents are the core platform team. They originate opportunities, build teams, support execution, and provide judgment where automation is not enough.

• What does the platform provide?

  Opportunities (validated ventures), teams (designed, not random), infrastructure (legal, tech, ops), growth support (marketing, sales) and an ownership system (transparent, dynamic).

• Do I need to deal with legal or admin work?

  No. The platform handles the full administrative and operational layer so you don't get blocked by non-core work: company setup and legal structure, invoicing and client billing, contracts, permissions and certifications, ongoing administrative operations, accounting and tax management. The platform also supports client-side operations: following up on payments, managing administrative relationships with clients, ensuring compliance and documentation. You don't run the company administratively — you build the company.

Risk & expectations

• What are the risks?

  Not all projects succeed. Time may not always translate into returns. However: no financial risk, no legal exposure, and a portfolio approach reduces downside. You take execution risk, not structural risk.

• Why are teams small?

  Because small teams of senior operators, supported by AI, outperform large teams. Higher speed, higher ownership, higher accountability.

• Why this model works now?

  AI reduces build cost. Distribution becomes the bottleneck. Talent + judgment becomes the key asset.