--- title: "A 90-day plan for your first business executive in a scientific team" description: "A three-phase plan for a senior commercial hire joining a research-led company: immersion, then mapping and translation, then co-creating the roadmap." url: "https://dmassociates.xyz/journal/a-90-day-onboarding-plan-for-integrating-your-first-business-executive-into-a-deeply-scientific-team/" --- Deep Tech # A 90-day plan for your first business executive in a scientific team 9 July 2025 · Last checked 18 October 2026 After an exhaustive search, you have hired your first senior business executive: an experienced leader joining as chief executive, chief product officer or chief revenue officer. They arrive on their first day ready to build financial models, craft go-to-market strategies and engage investors. Meanwhile your scientific team, the core of the venture, continues its work on a different clock, speaking a different language, driven by the pursuit of discovery. The moment these two worlds meet is one of the most dangerous and opportunity-rich inflection points in a company’s life. Without a deliberate plan, organisational antibodies activate, and the result is mistrust, miscommunication and two separate, competing cultures under one roof. Standard HR onboarding is not enough. What is needed is a strategic, 90-day **cultural integration mission** whose sole purpose is to build trust, credibility and shared understanding between the new executive and the founding scientific team. ## Phase 1, the first 30 days: deep immersion and earning credibility The goal for the first month is not for the executive to *act* but to *listen, learn and absorb* . Their first task is to earn the respect of the scientists, not by talking but by demonstrating humility and a genuine desire to understand. - Lab coat over suit. The executive should spend at least 40% of their time physically or virtually alongside the science team. They should shadow technical meetings, observe experiments where appropriate, and be a quiet presence where the real work happens. - Assign a science guide. Pair the new executive with a respected, patient member of your R&D team who can act as guide and translator, helping them navigate the internal wiki and the foundational research papers. - Run a listening tour. The executive conducts structured, 30-minute, one-to-one meetings with every member of the scientific and engineering team. The key questions are not about business but about the work: - “What is the most exciting problem you are working on right now?” - “What is the biggest obstacle to your progress?” - “What do you wish the business side of the company understood about your work?” ## Phase 2, days 31 to 60: mapping and translating With a foundation of earned trust, the executive shifts from pure absorption to sense-making. The goal is to begin building the bridge between the technology and the market. - Create the bridge document. The executive’s primary deliverable for this phase is a presentation mapping the current technical roadmap to potential commercial milestones and market opportunities. This forces them to synthesise what they have learned and articulate it strategically. The document is for internal discussion only. - Deliver a first small win. The executive identifies one non-critical operational bottleneck that has been frustrating the R&D team, such as slow procurement of lab equipment or a cumbersome software licence process, and uses their business experience to resolve it quickly. This demonstrates tangible value and builds goodwill. - Facilitate the first science-for-business roundtable. The executive organises and chairs a meeting where a few scientists present their work to the founder and other stakeholders, with the executive acting as translator and making sure the commercial implications are clearly understood. ## Phase 3, days 61 to 90: aligning and co-creating Now, and only now, can the executive begin to execute on their core mandate. With credibility established and the landscape mapped, they can move to co-creating the path forward. - Co-create the integrated roadmap. Working as a partner to you and your technical leads, the executive facilitates the building of the company’s first genuinely integrated technology and business roadmap, using the bridge document as a starting point. - Establish the leadership operating cadence. The executive puts in place the formal meeting rhythms, such as a weekly vision council and a leadership sync, that institutionalise communication between the scientific and business functions. - Deliver the 90-day plan. The executive presents their findings from the listening tour, the bridge document and the newly co-created integrated roadmap to you and the board. This presentation marks the formal end of onboarding and the transition into a fully operational leadership role. A disciplined 90-day mission does more than onboard a person. It fuses two cultures, and builds the foundation of mutual respect and shared language that the long journey ahead depends on. Written by Dineshwara Manideepu, founder of DM & Associates. [How we work with deep tech founders →](https://dmassociates.xyz/advisory/deep-tech/) [More from the journal](https://dmassociates.xyz/journal/) [Book a call](https://bookings.dmassociates.xyz/#/362591000000049559) ## Related reading - Deep Tech · Sept 2025 [The modern AI pricing dilemma](https://dmassociates.xyz/journal/the-modern-ai-pricing-dilemma/) How to price a generative AI product when inference costs vary with use and the underlying models keep getting cheaper every few months. - Deep Tech · Sept 2025 [Why trust is the essential moat for AI startups](https://dmassociates.xyz/journal/why-trust-is-the-essential-moat-for-ai-startups/) When model performance becomes a utility, defensibility shifts to reliability, transparency and fairness. How to build and measure that. - Deep Tech · Sept 2025 [Your first 100 users: a go-to-market playbook for vertical AI startups](https://dmassociates.xyz/journal/your-first-100-users-a-go-to-market-playbook-for-vertical-ai-startups/) Why SaaS growth playbooks fit vertical AI poorly, and what to do instead: one critical workflow, deep integration, and an enabled internal champion.