Seed-Stage Innovation Scorecard (Spreadsheet Template)
As an Amazon Associate I earn from qualifying purchases. Product links on this page are affiliate links — they cost you nothing extra.
⏱ 19 min read
What a Seed-Stage Innovation Scorecard Measures
A seed-stage innovation accounting scorecard measures evidence of customer behavior and market validation rather than projected revenue or short-term profitability. At this gate, review teams evaluate whether a specific problem exists, whether target users actively seek a solution, and whether initial unit economics can scale under real-world operational constraints. Auditable indicators like prototype sign-up conversion rates, customer commitment hours, and evidence velocity replace traditional Return on Investment (ROI).
Innovation accounting is an alternative performance measurement system designed for early-stage initiatives facing extreme market uncertainty, where standard financial metrics cannot reflect true progress. It tracks how quickly teams convert untested assumptions about customer problems into verifiable behavioral data before capital is committed to full-scale execution.
When organizations force seed-stage concepts through standard financial models, they guarantee distorted evaluations. In The Innovator’s Dilemma, Harvard Business School professor Clayton Christensen documented how discounted cash flow (DCF) models systematically bias established enterprises against disruptive concepts. Calculating a 5-year Net Present Value (NPV) or Internal Rate of Return (IRR) requires plugging in fixed assumptions about addressable market size, unit cost, and adoption timelines. Because those inputs do not yet exist for a nascent concept, teams simply fabricate revenue growth curves in Microsoft Excel to survive the capital committee.
Research by Harvard Business School senior lecturer Shikhar Ghosh found that approximately 75% of venture-backed startups fail to return their invested capital. Many of these doomed ventures cleared early financial hurdles by presenting polished 5-year models showing immediate 30% operating margins. Traditional financial metrics reward plausible spreadsheets, not validated reality. Adopting agile innovation accounting forces leadership to abandon financial forecasting in favor of empirical learning milestones.
Recommended gear
Innovation Accounting: A Practical Guide For Measuring Your Innovation Ecosystem's Performance
Innovate confidently with Innovation Accounting: A Practical Guide for Measuring Your Innovation Ecosystem's Performance, ensuring your company's growth through robust innovation metrics.
Affiliate link
This dynamic exposes the primary governance failure inside corporate incubators: review boards routinely judge presentation polish rather than inspecting auditable customer evidence. You have likely sat through these sessions. A team enters with 20 impeccably designed slides, glowing customer quotes, and an endorsement from a business unit vice president. The committee approves $250,000 in seed tranche funding because the meeting felt compelling.
Disciplined capital allocation requires a fundamental shift in review behavior. The review panel must act like forensic auditors rather than a judging panel at a startup competition. They must decline to evaluate charisma, slide design, or narrative confidence. Instead, they inspect receipts:
- Did at least 15 out of 20 target users execute a critical manual task during an uncompensated 45-minute usability sprint?
- Did 8 commercial prospects sign a non-binding letter of intent (LOI) to run a pilot at a target price of $1,200 per month?
- Did a simple landing page smoke test generate a minimum 12% click-through rate from 500 targeted enterprise ad impressions within 14 days?
Aligning these thresholds with your corporate understanding of risk appetite in innovation prevents executives from overriding measurable behavioral hurdles with gut instinct.
| Myth | Fact |
|---|---|
| Seed-stage projects need a five-year pro-forma income statement to secure funding. | Pro-forma statements at this stage are pure guesswork; gates must require behavioral proof of customer pain points. |
| User surveys and focus groups provide reliable evidence of market demand. | Declared intent is notoriously inaccurate; only skin-in-the-game actions (time invested, deposits paid, data shared) count as validation. |
| Killing a project at the seed gate represents wasted capital and initiative failure. | Halting an unvalidated concept after an initial 8-week sprint protects capital and frees talent for higher-probability opportunities. |
| The team that builds the fastest prototype wins the seed gate review. | Speed of learning matters more than speed of coding; the winning team is the one that invalidates key assumptions quickest. |
When your governance process transitions from approving slide decks to auditing concrete customer interactions, the composition of your gate template must follow suit. Looking at the exact metric weights and data structures in the gate scorecard template below reveals how to automate these pass-fail thresholds directly inside your own workflow.
Key Takeaways
- Replace revenue forecasts with validated learning thresholds: problem severity, solution interest, and commitment evidence.
- Allocate capital in metered tranches based on hypothesis testing velocity rather than project milestones.
- A validation score above 70% clears early ventures to proceed from discovery into prototype testing.
Table of Contents
- What a Seed-Stage Innovation Scorecard Measures
- Core Evaluation Pillars Across the Seed Gate
- Scoring Mechanics and Stage-Gate Weighting Rules
- Governance Rhythms for Innovation Review Boards
- The Seed-Stage Innovation Scorecard Spreadsheet Template
- Sources & Further Reading
Core Evaluation Pillars Across the Seed Gate
The seed-stage gate requires early ventures to clear strict empirical thresholds across three distinct pillars—desirability, feasibility, and viability—before earning follow-on capital. A seed-stage gate is a formal corporate governance checkpoint where an internal venture must present measurable evidence of customer demand and technical reality to secure dedicated budget for a live pilot. Without hard metrics at this juncture, steering committees default to funding executive pet projects and slick slide decks.
Desirability Validation Criteria
Opinion-based feedback is useless at the seed gate. To prove customer pull, teams track problem frequency, urgency scores, and unprompted sharing rates using structured discovery protocols like a VOC Translation Matrix (With 5-Step Template). Problem frequency measures how often the target user encounters the friction: a B2B workflow pain must occur at least 3 times per business week to justify changing user habits.
Urgency scores measure how actively users seek a fix right now. In user interviews, evaluate whether the user has dedicated existing budget or hacked together an internal workaround (like an unwieldy spreadsheet macro). If fewer than 60% of interviewed prospects report an active workaround, urgency is too weak to support a commercial launch.
Unprompted sharing rates provide the final desirability filter. In Alberto Savoia’s book The Right It, customer commitment is measured through concrete "skin in the game" actions rather than polite praise. When 15% or more of interview participants introduce the project team to a peer without being prompted or incentivised, the venture clears the desirability bar.
Feasibility Boundaries
Feasibility screening protects your organisation from sinking budget into solutions it cannot legally operate or technically deliver. Teams must document foundational technical blockers, core architectural dependencies, and compliance limits inside an Agile Innovation Accounting system. A technical blocker exists when a proposed product requires infrastructure or latency performance that your enterprise stack cannot currently support.
Every internal venture must run a mandatory 2-week architectural review spike before the gate meeting. This review maps every external API dependency and legacy database integration. If an initiative relies on more than 2 unverified third-party APIs with service level agreements below 99.9%, the engineering lead must flag it as high-risk.
Regulatory constraints act as binary go/kill triggers rather than soft targets. For regulated fields like financial services or healthcare, an enterprise cannot fund prototypes that breach GDPR data residency rules or regional compliance guidelines. Teams should calibrate these boundaries directly against the enterprise portfolio mandate outlined in Understanding Risk Appetite in Innovation.
Viability Proxies
Monetary revenue rarely exists at the seed stage, so evaluation committees require non-monetary currency exchanges as commercial proxies. When prospective buyers cannot legally pay for an unreleased product, track their willingness to spend scarce resources: calendar time, proprietary data access, or formal commitments. As noted in research published by the Harvard Business Review, measuring early behavioral commitment predicts eventual market adoption far more accurately than customer sentiment surveys.
Time investments show genuine commercial intent. A enterprise buyer who commits 4 hours of senior staff time across 3 sprint feedback sessions has staked professional capital on your solution. If a prospect refuses to dedicate 30 minutes of team review without a vendor gift card, viability is functionally zero.
Letters of intent (LOIs) and pre-orders represent the ultimate viability signal before coding begins. An LOI is a signed, non-binding business document stating that a customer intends to purchase the software if it meets specified functional criteria within 6 months. Achieving at least 3 signed corporate LOIs or 50 customer deposits confirms commercial viability and earns a gate pass.
The Seed Gate Evidence Matrix
False Dawn
Intense user excitement paired with prohibitive compliance or tech blockers.
Belongs here if: Desirability score exceeds 75% but regulatory approval timeline exceeds 18 months.
Then: Pause feature work immediately and assign a 3-week technical spike to resolve the bottleneck.
Technical Sandbox
Elegant, compliant engineering architecture that solves an infrequent user problem.
Belongs here if: Feasibility is fully cleared but target problem occurs less than once per month.
Then: Kill the project or pivot the core technology to a higher-frequency customer pain point.
Commercial Trap
High user interest and easy build feasibility, but zero customer willingness to commit resources.
Belongs here if: Prototype passes UX tests but team secures zero LOIs or data-access permissions in 30 days.
Then: Freeze engineering budget until prospects exchange documented organizational time or funding.
Fundable Horizon
Verified urgency, cleared compliance roadmaps, and documented prospective commitments.
Belongs here if: Initiative meets defined minimum thresholds across desirability, feasibility, and viability proxies simultaneously.
Then: Release tranche-one build capital and advance the venture directly to the pilot stage.
When team members bring their raw findings to the gate, they often dispute how these signals translate into a pass, kill, or pivot decision. Next, see the exact spreadsheet formulas and numerical weights that convert these ambiguous indicators into a hard, automated score.
Scoring Mechanics and Stage-Gate Weighting Rules
Seed-stage scorecards must weight customer desirability at 50%, business viability at 25%, and technical feasibility at 25% to prevent teams from building products nobody wants.
Innovation accounting is an evaluation framework that measures early-stage venture progress through empirical evidence of customer behaviour and validated learning rather than standard financial projections or delivery milestones.
Without this structure, teams default to measuring activity instead of validation. A software team might write 10,000 lines of code and hit every sprint deadline, yet produce a service that solves no urgent commercial problem. Calibrating your scorecard around empirical validation stops this waste before development costs escalate.
The 1-to-5 Evidence Strength Scale
Most internal scoring models fail because they treat an interview quote the same as a customer deposit. In their framework for business experimentation, authors David Bland and Alexander Osterwalder at Strategyzer establish that evidence strength depends on customer commitment. What people say in a 20-minute survey rarely matches what they do when their budget or time is on the line.
Your scorecard must calibrate evidence along a strict 1-to-5 scale:
- Score 1 (Opinion): Internal team assumptions, desk research, or competitor audits. Zero direct customer interaction.
- Score 2 (Stated Intent): Customer surveys, focus group transcripts, or verbal expressions of interest. The customer has spent zero currency, time, or social capital.
- Score 3 (Observed Behaviour): Click-through rates on mock ad campaigns, sign-ups on a feature landing page, or documented interactions with a clickable prototype.
- Score 4 (Non-Monetary Commitment): The customer trades valuable resources other than cash. Examples include providing proprietary datasets for a 14-day proof of concept, completing a 60-minute technical discovery session, or agreeing to a public case study.
- Score 5 (Financial Commitment): Binding commercial proof. This requires a signed letter of intent with financial penalties, a non-refundable cash deposit (such as a $500 pre-order reservation fee), or a live pilot purchase order.
Embedding this scale into your agile innovation accounting system stops teams from presenting vanity metrics as project success.
Stage-Gate Weighting Distribution
Early-stage projects die from lack of market demand, not lack of code. According to research by CB Insights on startup failures, 35% of failed ventures cite building products with no market need as the primary cause of death.
Your scorecard’s math must reflect this reality by applying the 50-25-25 distribution:
- Desirability (50% Weight): Answers whether the market cares about the problem. It scores the evidence that target users experience this acute pain point and actively seek an alternative to their current workaround.
- Viability (25% Weight): Answers whether the unit economics work. It measures evidence around willingness to pay, gross margins, estimated customer acquisition cost, and regulatory compliance.
- Feasibility (25% Weight): Answers whether your team can build and deliver the solution. At the seed stage, technical hurdles are rarely the main hazard unless the venture relies on novel deep tech or patents.
To calculate the composite gate score, multiply each domain’s raw 1-to-5 score by its assigned weighting. A project that earns a 4 in desirability, a 2 in viability, and a 5 in feasibility earns a composite score of 3.75 out of 5.00:
(4 * 0.50) + (2 * 0.25) + (5 * 0.25) = 2.00 + 0.50 + 1.25 = 3.75
Aligning these weighting rules with your organisation’s explicit guidelines for understanding risk appetite in innovation prevents governance boards from debating feelings instead of evidence.
The Desirability Veto Rule
A high composite score can hide a fatal project flaw. If an engineering team scores a 5 in feasibility by building a functioning system, and a 4 in viability by constructing a high-margin financial model, the project would achieve a passing grade of 2.25 out of 5.00 even with a zero in customer demand.
The scorecard prevents this via an absolute veto rule: Any venture scoring below 3.0 in Desirability triggers an automatic gate failure.
When the veto trips, the stage-gate committee has only two options. The team must pivot its problem-solution hypothesis back to customer discovery, or leadership must close the project immediately to release funding. High technical feasibility or high projected margins cannot compensate for a lack of verified customer demand.
How to Run the Scoring Review
- Audit the evidence log: Collect the test cards and validation results from the team 48 hours before the gate meeting.
- Assign base scores: Review the highest level of validated commitment for each dimension using the 1-to-5 evidence scale.
- Apply the veto test: Check the raw Desirability score; if it falls below 3.0, halt the agenda and discuss pivot or closure scenarios immediately.
- Calculate weighted totals: Multiply the raw scores by the 50-25-25 distribution to generate the final composite gate number.
- Issue funding tranche: Release seed capital only if the project clears the minimum hurdle score set in your scorecard template.
Once you lock down your weighting rules and establish clear threshold criteria, the next challenge is translating these raw calculations directly into your spreadsheet cells to automate pass-or-pivot flags across multiple project teams.
Governance Rhythms for Innovation Review Boards
An Innovation Review Board governs seed-stage initiatives through monthly 30-minute metered funding check-ins rather than annual corporate budgeting cycles. Metered funding is an investment approach where an organization releases capital in small tranches only after an innovation team validates specific business assumptions with real customer data.
Annual budgeting systems encourage teams to build slide decks and burn cash for 12 months before revealing whether a market exists. In The Lean Enterprise, authors Trevor Owens and Obie Fernandez note that releasing capital in controlled increments between $20,000 and $50,000 prevents ventures from exhausting significant capital before testing customer demand. You replace the quarterly stage-gate review with a recurring 30-minute operational sync:
- First 5 minutes: The venture lead states the single falsifiable hypothesis targeted during the prior cycle.
- Next 15 minutes: The team presents raw test evidence, customer interview records, or live traffic data.
- Final 10 minutes: The review board votes on the next tranche using principles of Agile Innovation Accounting.
[30-Min Review Board]
|
v
[Evidence Velocity Check]
|
+-----------+-----------+
| | |
v v v
[Alpha] [Pivot] [Shutdown]
Next Tranche 30-Day Run Archive
The primary metric governing these board votes is evidence velocity. Evidence velocity is the operational metric that measures how many customer-facing hypotheses a venture team tests and resolves against each dollar of capital spent over a delivery cycle.
If Team A spends $30,000 over 6 weeks and disproves 12 risky assumptions about unit economics, their velocity is 0.4 resolved hypotheses per thousand dollars. If Team B spends $30,000 writing backend architecture without exposing a single proposition to a buyer, their velocity is zero. In The Startup Way, author Eric Ries notes that evaluating internal startups by milestones of validated learning protects enterprise capital far better than measuring adherence to an upfront project schedule. Incorporating these metrics into your broader process helps your organization manage innovation budgets with precision.
Dan Toma and Esther Gons demonstrate in their framework on corporate governance that review boards should avoid subjective debates by evaluating only empirical proof.
Pro-Tip: Never let project teams present formatted slide decks during these 30-minute meetings. Have board members inspect live data logs, signup conversion dashboards, and recorded customer discovery interviews directly inside your tracking workspace.
Every check-in must conclude with one of three explicit, binding decisions:
- Clear the Gate to Alpha Testing: The team produced validated metrics on customer acquisition and willingness-to-pay. The board releases the next metered tranche—typically between $75,000 and $150,000—to build a functioning alpha test for private user trials.
- Targeted 30-Day Pivot Sprint: The data disproved the initial channel or packaging assumption, but uncovered verified buyer pain in an adjacent workflow. The board releases a strictly capped $15,000 bridge budget for a rapid sprint to validate the new path.
- Graceful Shutdown: The evidence proves that user acquisition costs outrun customer lifetime value, or that customers will not alter their current behavior. The board ends funding immediately and archives all test data in a central registry.
Deciding to close a project early is an operational success, not an operational failure. Amy Edmondson, Professor of Leadership and Management at Harvard Business School, classifies these outcomes in her research on psychological safety as intelligent failures that generate actionable knowledge at low cost. Documenting these results supports the psychology of failure in innovation across your business units while aligning decisions with your defined risk appetite.
Pro-Tip: Measure your review board on its kill rate. If your board funds more than 25% of seed-stage concepts past the second tranche, your members are approving initiatives based on organizational politics rather than objective evidence.
Once you establish these governance boundaries, you need an objective spreadsheet tool to score these tranches without manual recalculations during live meetings.
The Seed-Stage Innovation Scorecard Spreadsheet Template
A seed-stage innovation scorecard spreadsheet converts subjective venture progress into objective investment decisions through a three-tab architecture linking unproven assumptions directly to metered capital releases.
Innovation accounting is a disciplined framework of leading indicators designed to evaluate early-stage ventures against validated milestones rather than traditional lagging financial metrics like revenue or net profit. Instead of funding annual budgets up front, investment committees allocate capital in tranches—such as $50,000 for proof of concept or $150,000 for pilot testing—based on verifiable evidence gathered during discovery sprints.
The Three-Tab Spreadsheet Architecture
The downloadable model structures raw uncertainty into clear gate evaluations through three interconnected tabs:
[Tab 1: Assumption Log]
|
v
[Tab 2: Gate Scorecard]
|
v
[Tab 3: Executive Summary]
- Tab 1: Assumption Log. Every venture starts as an unvalidated hypothesis. This tab captures each leap-of-faith assumption, categorises it by risk type (Desirability, Feasibility, Viability, or Governance), and assigns a criticality score from 1 to 5. Teams document the exact test method, target completion date, owner, and the binary pass/fail evidence threshold needed to clear the risk.
- Tab 2: Gate Scorecard. This is the core evaluation engine. It houses 12 standardised test gates across the four risk categories. Each gate tracks the baseline target, the actual observed metric, an automated variance calculation, and a weighted score out of 100.
- Tab 3: Portfolio Summary. Designed for corporate venture boards and investment directors, this tab aggregates scores across active projects. It applies conditional formatting to flag projects as Fund (score \(\ge 80\)), Pivot (score 60–79), or Kill (score \(< 60\)), directly informing next-tranche capital allocations.
If your team needs to formalise this evaluation cadence into structured review cycles, running a disciplined Agile Innovation Accounting workflow keeps validation cycles locked to two-week iterations.
The 12-Gate Evaluation Rubric and Baseline Benchmarks
In their field guide Innovation Accounting, authors Dan Toma and Esther Gons note that early-stage teams fail most often by measuring vanity metrics—such as site visits or customer meetings—rather than true evidence of value commitment.
The evaluation tab implements 12 quantitative and qualitative gates. Each gate requires a specific proof threshold before the spreadsheet awards points toward the seed-gate milestone:
| Gate Category | # | Test Gate Name | Baseline Benchmark Threshold | Measurement Method |
|---|---|---|---|---|
| Desirability | 1 | Problem Resonance | \(\ge 70\%\) target pain severity | 20+ qualitative customer discovery interviews |
| 2 | Value Proposition Fit | \(\ge 40\%\) "very disappointed" score | Sean Ellis product-market fit survey method | |
| 3 | Demand Pull | \(\ge 15\%\) call-to-action conversion | Smoke-test landing page signup rate | |
| 4 | Letter of Intent (LOI) | \(\ge 3\) non-binding corporate LOIs | Signed preliminary customer interest agreements | |
| Feasibility | 5 | Core Tech Usability | \(\ge 80\%\) unassisted task completion | 10 moderated usability test sessions |
| 6 | Architecture Proof | \(\le 1.5\text{s}\) latency at 500 requests/sec | Technical benchmark run on prototype environment | |
| 7 | Delivery Dependency | 0 critical single-point vendor risks | Vendor risk audit and secondary sourcing review | |
| Viability | 8 | Unit Economics Floor | Estimated LTV:CAC \(\ge 3.0\) within 18 months | Financial sensitivity model based on test CAC |
| 9 | Willingness to Pay | \(\ge 25\%\) deposit or pre-order payment | Currency commitment test on pilot checkout | |
| 10 | Addressable SAM Size | \(\ge \$100\text{M}\) reachable served market | Top-down industry analysis verified by bottom-up data | |
| Governance | 11 | Strategic Alignment | \(\ge 80\%\) executive rubric alignment | Corporate innovation thesis match score |
| 12 | Compliance Clearance | 100% legal, IP, and data sign-off | Formal legal review on regulatory and IP exposure |
Step-by-Step Setup: Adjusting Category Weightings
Venture risk profiles vary by sector and corporate mandate. A consumer software app requires aggressive desirability validation, while an enterprise platform might live or die on feasibility and governance.
To tune the spreadsheet’s scoring algorithm to your specific context, follow these three steps in the settings sheet:
- Audit Corporate Strategic Mandates. Open cell range
B4:B7on theSettingstab. By default, the template applies balanced baseline weights: Desirability (35%), Feasibility (25%), Viability (25%), and Governance (15%). - Reallocate Percentage Points. Adjust the weightings to match your operating environment. For instance, teams balancing core upgrades against radical bets using the Manage Innovation Budgets: 70-20-10 (Excel Template) often lift Governance and Strategic Alignment to 30% to prevent strategic drift. Verify that cell
B8sums to exactly 100%. - Lock Benchmark Cells. After setting the category weights, lock the reference columns (
C12:C24on theScorecardtab). This prevents discovery teams from changing gate pass/fail targets during sprints when data comes in lower than anticipated.
Which Venture Path Fits You?
If you are operating in a strictly regulated environment (clinical, pharma, or medical device)…
Regulatory approvals and patent barriers outweigh early conversion tests. Increase the Feasibility and Governance weights to 35% each, lower Desirability to 15%, and evaluate your progress against the Healthcare Innovation Scorecard: 10 Metrics (Template) to address compliance milestones early.
If you are building an internal B2B enterprise SaaS solution…
Customer discovery and willingness-to-pay signals matter most before writing enterprise code. Keep Desirability at 40%, set Viability at 30%, Feasibility at 20%, and Governance at 10%. Require at least three signed Letters of Intent (Gate 4) before releasing engineering funds.
If you are spinning out an external venture backed by corporate capital…
External competition requires swift proof of market scalability. Set Viability to 40%, Desirability to 30%, Feasibility to 20%, and Governance to 10%. Focus heavily on Gate 8 (Unit Economics Floor) and Gate 9 (Willingness to Pay) to ensure the venture can raise institutional follow-on rounds.
Download the scorecard spreadsheet template, open the Assumption Log, and enter your team’s top three unvalidated commercial risks today to establish your initial gate review baseline.
Sources & Further Reading
A seed-stage innovation accounting scorecard relies on rigorous evidence gates that replace speculative revenue forecasts with auditable milestones of customer commitment.
Innovation accounting is a framework for tracking early-stage venture progress through measurable indicators of customer validation, hypothesis testing, and learning velocity rather than conventional profit-and-loss statements.
Without objective scorecards, project teams default to vanity metrics that disguise flawed assumptions. Research by CB Insights examining 111 startup failures revealed that 35% collapsed because they built products with zero market need. When evaluation gates require observable customer actions—such as a 15% conversion rate on an unbranded landing page or 20 completed discovery interviews within a 4-week discovery cycle—capital allocation shifts from political persuasion to objective validation.
To build an evaluation model that satisfies both venture leads and corporate finance teams, review the foundational literature on governance and validation design.
Writing in the Harvard Business Review, Steve Blank highlighted that business plans rarely survive first contact with customers, making hypothesis scorecards essential for early-stage portfolio survival. Teams should calibrate each scoring dimension so that seed teams release tranches of capital—often limited to $25,000 or $50,000 increments—only when core behavioral hypotheses achieve statistical significance.
- Eric Ries, The Lean Startup, 2011: Establishes the core principles of innovation accounting, validated learning milestones, and baseline cohort metrics.
- Dan Toma and Esther Gons, Innovation Accounting, 2021: Supplies the operational framework for designing multi-tiered indicator scorecards across corporate governance levels.
- Robert G. Cooper, Winning at New Products, 2017: Details the mechanics of formal Stage-Gate systems and objective gate-readiness criteria for development projects.
- Steve Blank, The Four Steps to the Epiphany, 2005: Formulates the customer discovery gating steps that prevent premature capital expenditure.
- CB Insights, "The Top 12 Reasons Startups Fail", 2021: Provides empirical failure data demonstrating why early evidence criteria must precede product development.
Featured image by Alena Evseenko on Pexels