aizatto.com
  • aizatto.com
  • Table of Contents
  • Portfolio, Projects, Tools, Toys
  • Interview Guide
    • Choosing A Company
    • Job Boards
    • Practice
    • Technical Interview Cheatsheet
    • Interview Process
      • Questions to Ask
      • Coding
      • Soft Skills
      • Rejection
      • Negotiation / Deciding
      • Accepting, Joining
    • FAQ
  • Engineering Code
    • Communication
    • Different Types of Coding
    • Commit Messages
    • Reviewing Code
      • Requesting Changes
    • Writing Code
      • Consistency
      • Writing for a code base of 1,000,000+ Lines
      • Write Code Knowing It Will Be Refactored
      • Naming
        • Versioning
        • Create Searchable Names
      • Commenting
        • Don't commit commented code
      • Make It Easy To Reproduce
      • Scripts
      • 80 character limit
      • Exit Early
      • Be careful of enum in switch statements
      • Be careful about chaining conditions
      • Be careful of chaining ternary operators
      • Write Code Knowing You Will be Blamed
      • Hacks
      • Bad Practices
      • Logs
      • Time
      • Other rules
    • Engineering Code
    • Engineering Data
    • Pipelines
    • Configuration Files
    • Site Reliability Engineering (SRE)
    • Best Engineers
  • Engineering Management
    • Hiring
    • New Reports
    • 1:1s
      • Calibration
      • Expectations
      • Mentorship / Learning / Growing
      • Task Management
      • Teams
    • Interviewing Candidates
    • Messenger Groups
    • Resources
  • Why GitBook?
  • Getting into Tech
    • Terminology
  • Personal Goals
  • Daily Drivers
  • Contacting Me
  • Notes
    • JavaScript
      • Array
      • Async & Await / Promises
      • Booleans
      • Collections
      • Cons/Dislikes
      • fetch
      • Map
      • Modules
      • Object
      • Regex
      • Set
      • Style Guides
      • Versions
    • Node.js
      • Best Practices
      • DraftJS
      • eslint
      • GraphQL
      • Relay
      • Hapi
      • Knex
      • Koa
      • TypeScript
      • Webservers
    • Technical Due Diligence
    • Archive
      • Amazon Echo Dot (3rd Gen) with clock
      • Apple
        • AirPods Pro
        • Apple Notes
        • Apple Watch Series 4
        • iPad Pro 11" 2018
        • MacBook Pro 15" 2017
        • macOS
      • Audible
      • Balance
        • Growth vs Contentment
        • Leading vs Following
        • Mindful vs Mindless
        • New vs Old
      • Bags
      • Bandwidth Requirements
      • B2B/B2C
      • Blockchain
      • Board Games
        • Bang
      • Broadway
      • Cheap, Good, Fast
      • CLI
        • git
        • ufw
        • xargs
      • Cloud Providers
        • GCP
      • Communication
        • Asking Questions / Making Requests
        • Making Edits
        • Synchronous vs Asynchronous
        • Change Management
        • Problem Definition
      • Company
        • All Hands
        • The Problematic CTO
        • Organizational Structure
      • Content Creation
      • COVID 19/Corona Virus
      • Coworking Spaces
      • Daily Routine
      • Dating
      • Displays / Monitors
      • DNS
      • Domain Registrars
      • Driving
      • eCommerce
      • Empire Building
      • Facebook for Developers
      • Fever
      • Fiverr
      • Flights
      • Gaming Tablet
      • GitHub
      • GTD
      • Go Lang
      • Headsets
      • Hiking
        • Chamang Waterfalls
        • Kanching Waterfalls
        • Kota Damansara Community Forest Reserve
        • Sungai Chilling
      • Home Device Calling
      • iCalendar
      • Keyboards
        • Ergodox Ez
      • Malaysia Insurance
      • Mental Health Malaysia
      • Multiroom Wireless Speaker System
      • Musicals
      • Mouse
      • Movies
      • Password Managers
      • Phabricator
      • Physical Health
        • Cardio
      • Podcasts
      • Programming Bootcamps
      • Property
      • Productivity
        • Note Taking
      • Redang
      • Relationships
      • Referral Codes
      • Remote Calls
      • Remote Work
        • Comparison
      • Road Trips
      • Ruby / Ruby on Rails
      • Scraping
      • Slack
      • Stripe
      • Singapore
      • UX
      • Venture Builder
      • Video Games
      • Virtual Personal Assistant
      • VPN
      • WebDAV / CalDAV
      • WebSocket
      • Withings
      • Xiaomi Roborock Mijia
      • Old Hardware
        • Netgear R7000P
      • Web Development
        • React
        • SSO Providers
      • Software Engineering
        • Software Architectures
          • Monolithic
          • Non-Monolithic
            • Microservice
            • FaaS (Functions as a Service) or Serverless
        • Repository Management
  • More on Notion
Powered by GitBook
On this page
  • Goals of a Technical Due Diligence
  • Sub Goals
  • Caveats
  • Timeline
  • Findings
  • Red Flags, Problems, Issues
  • Deal Breakers, Show Stoppers

Was this helpful?

  1. Notes

Technical Due Diligence

I've been aiding investors to conduct their Technical Due Diligence to asses the risk of investing into Startups.

When conducting a Technical Due Diligence (DD or TDD), the question I am trying to answer is:

What are the deal breakers in this investment?

To answer this, I need to identify:

  • What does the investor consider a dealbreaker?

    • What are potential dealbreakers they may not even realize?

    • What is the investors investment thesis?

  • What are the potential dealbreakers in this company?

  • Is there anything specific you'd like me to investigate?

  • How would they like me to deliver findings?

Goals of a Technical Due Diligence

  • Identify risks for Investors

    • Find Deal Breakers, and Red Flags

Sub Goals

  • Can the tech team deliver on the product roadmap?

    • What is the product roadmap?

Caveats

  • A TDD can also turn into a Product Due Diligence

    • How well can the tech team support their product?

    • Be prepared to discuss about product roadmap if there are no technical problems.

Timeline

When I am connected with a potential company, I provide a timeline:

Call:

  • 30 Minutes max

  • Introductions

  • Explain the Technical Due Diligence process

  • Learn a bit more about the company

  • Explain any documentation that is required to fill

  • Figure out a single point of contact

Onsite:

  • 1-2 days

  • Demo of the product

    • Helps to inform architecture and infrastructure questions

  • Demo of the internal tools

  • Product roadmap

  • Individual meetings with heads of different product. Departments

    • 30 minutes max

  • Architecture review

  • Understanding Development process

  • Individual meetings with senior leadership

    • Members: CTO, CPO, senior engineers

    • 30 minutes max

  • Join release/deployment process

  • ERD of databases

    • Understand data structure

  • Let me know if any meetings are with remote employees

    • I can schedule my time better knowing so

Findings

I categorize findings into two areas:

  1. Red Flags, Problems, Issues

  2. Deal Breakers, Show Stoppers

Red Flags, Problems, Issues

If I find any of these, for the most part, I find these as a "pass". I do note them down, but everything has a problem. I only escalate these findings into "Deal Breakers" if upon diving a little deeper into it, you discover deep fundamental problems.

For example:

Everyone has technical debt, but does the technical debt slow them down?

Deal Breakers, Show Stoppers

As the name suggests, these are the reasons why the deal should not be made. These are the risks that an investor has to be really aware of when investing.

Examples:

  • They are doing something illegal

  • They are outsourcing their work

  • They don't have the technical ability to deliver on their roadmap

  • They claim to be doing something they are not actually doing, or don't have the competency to

  • They are investing into new technology, they are not familiar with

"Deal Breakers" may not stop the deal, but do have a discussion with the investor about the investment thesis.

  • Are you investing into it being a profitable business?

    • These business may still be making money.

  • Are you investing into the company into building their technical expertise?

PreviousWebserversNextArchive

Last updated 3 years ago

Was this helpful?