Technology research

✅ Why this step helps you avoid dead ends (and find smart shortcuts)

You know who you’re building for and what they need—now figure out how it might work.

Technology research explores the tools, platforms, materials, and techniques that could bring your idea to life. It helps you understand what’s already available, what’s emerging, and what’s feasible within your time, cost, and capability limits. It reduces risk, accelerates design, and prevents wasted effort chasing the wrong tech.


📘 What you’ll investigate

  • Relevant hardware platforms, modules, or development kits
  • Off-the-shelf solutions vs. custom development trade-offs
  • Available sensors, chips, APIs, or cloud tools
  • Licensing, compliance, or supply constraints
  • Costs, lead times, and compatibility with your team or supply chain

🛠️ Tools and methods

✅ Tech Research Checklist

Identify core tech functions: sensing, power, communication, UI, etc.
Search for existing solutions: components, SDKs, libraries, kits
Evaluate feasibility: cost, availability, documentation, support
Look for emerging tools: new platforms or methods that could simplify the build
Track pros and cons: speed, scale, constraints, risks

Example Tech Research Table

FunctionOptions ConsideredProsRisks
ConnectivityLoRa, Wi-Fi, NB-IoTLoRa = low powerNB-IoT coverage varies
DisplayE-ink, OLED, LCDE-ink = great in sunSlow refresh rate
Control chipESP32, STM32, Raspberry Pi PicoESP32 = fast to devPico lacks deep sleep
  • Document findings in a central place—Notion, Airtable, or a shared doc
  • Revisit later as tech evolves—some “no” options may become viable later

⚠️ What to watch out for

  • Falling in love with a technology before validating the need
  • Choosing complex tech when simpler solutions exist
  • Not checking licensing, availability, or support status
  • Assuming “free” tools come without trade-offs

💡 From technical founders

“We spent three weeks trying to build a custom sensor—then found an off-the-shelf version for £2. Tech research doesn’t slow you down. It saves you.”

– CTO, AgriTech Pilot Startup

💡 Research the boring stuff too—like battery life, casing materials, or connector types. They’ll trip you up later if ignored now.


🔗 Helpful links & resources

  • Tech Research Mapping Template
  • Download: Feature–Tech Fit Grid
  • Article: How to Explore Technologies Without Getting Stuck in the Weeds
  • Follow-on: Viability Sprint

✍️ Quick self-check

Have we listed all the major functions the product must perform?
Are we aware of multiple options for each key function?
Do we know the trade-offs between custom vs. off-the-shelf?
Are our choices grounded in real constraints—cost, lead time, and build skill?

🎨 Visual concept (optional)

Illustration: A comparison board shows three tech options for “connectivity”. Each option has icons for cost, power, dev speed, and compatibility. A team member tags one “Risky but powerful”, another “Easy to prototype”.

Visual shows how structured tech research builds confidence and avoids unnecessary complexity before you commit.