Twin

What the project is

Twin is a mentorship platform that connects mentees, mentors, and administrators in one coherent product ecosystem. It includes a public-facing landing experience, an internal user application, an admin panel, and a backend API that powers all core business workflows.

The product goal is to make the full mentoring journey measurable and easy to manage: from first contact and onboarding, through matching and mission execution, to communication, progress tracking, and operational reporting.

What the project consists of

The project is a monorepo with several cooperating applications:

• Landing (`web/`): a Vite + React marketing site with localized content, access request flow, and mentoring compass flow.
• Admin (`admin/`): a Vite + React internal panel for operational management, content updates, and platform administration.
• API (`api/`): a NestJS backend with TypeORM and PostgreSQL, responsible for domain logic, integrations, authentication, and data consistency.
• Supporting scripts (`scripts/`): automation for local setup, database workflows, and repeatable developer operations.

Together, these parts provide one end-to-end product: acquisition, onboarding, matching, execution, and governance.

How we build it as a team with the client

We run the project as a collaborative product-engineering partnership, not just a handoff model.

• Shared discovery and prioritization: we refine requirements with the client, align on business outcomes, and define realistic milestones.
• Iterative delivery: we ship in small, reviewable increments so the client can validate direction early and often.
• Joint decision-making: architecture, UX, and scope decisions are discussed transparently, with trade-offs explained in business terms.
• Quality-by-default process: each change goes through code review, linting, tests, and environment validation before release.
• Feedback loop with users and stakeholders: client feedback and production insights are fed back into the backlog and roadmap.

This way of working keeps the product aligned with real user needs while preserving technical quality and long-term maintainability.

Team collaboration principles

• Single source of truth for requirements and acceptance criteria.
• Clear ownership with shared context across product, design, and engineering.
• Documentation where it adds value, especially around domain decisions and operational workflows.
• Continuous improvement in both the product and the delivery process.

In practice, Twin is built through close, ongoing collaboration between our team and the client, combining strategic product thinking with disciplined software delivery.