# Depotridge

*/Startups/Depotridge*

## Startup Overview

The platform normalizes fragmented warehouse telemetry into unified inbound forecasts. It ingests raw signal data across diverse logistics endpoints and translates disparate facility metrics into structured arrival schedules. Operators receive immediate visibility into incoming freight volumes without manually piecing together individual facility reports.

Supply chain planners and facility managers routinely face blind spots caused by disconnected warehousing systems. When relying on manual spreadsheet reconciliation or legacy EDI aggregators, teams are forced to operate on delayed batch cycles. This fragmentation leaves distribution centers understaffed during volume spikes or over-resourced during lulls.

Where visibility tools like Project44 require manual dashboard monitoring and legacy aggregators rely on delayed data dumps, this architecture is fully programmatic and streams continuously in real time. It eliminates batch delays and dashboard dependencies entirely, routing unified forecasting data directly into existing operational workflows to trigger immediate staging and labor allocation.

## Startup Founding Hypothesis

**Approach**: that normalizes fragmented warehouse telemetry into unified inbound forecasts
**Competitors**:
- [Manual spreadsheet reconciliation](/Competitors/Manual_spreadsheet_reconciliation)
- [Legacy EDI aggregators](/Competitors/Legacy_EDI_aggregators)
- [Project44](/Competitors/Project44)
**Differentiator2x2**: fully programmatic and real-time streaming, eliminating batch delays and manual dashboard dependencies

## Startup Solution Coordinate

**Solution**: [Inbound Telemetry Stream](/Software/Inbound_Telemetry_Stream)

## Startup Position2x2

```mermaid
quadrantChart
title Warehouse Telemetry Forecast Positioning
x-axis Manual Dashboard --> Programmatic API
y-axis Batch Delayed --> Real-time Streaming
Manual spreadsheet reconciliation: [0.15, 0.15]
Legacy EDI aggregators: [0.80, 0.20]
Project44: [0.65, 0.75]
Depotridge: [0.90, 0.90]
```

## Startup Offer

**Proof**:
- Aiming to reduce dock scheduling conflicts by 30% for high-volume regional 3PLs.
- Targeting the complete elimination of batch-processing delays for automated sorting facilities.
- Designed to achieve >99.9% mapping accuracy across fragmented legacy EDI payloads.
**Tiers**:
- Name: Developer Stream · Price: ~$0.01–$0.03 per ingested event · Inclusions: Self-serve API access for up to 3 distinct WMS or telemetry formats, intended for prototyping and capped at 100k normalized events per month.
- Name: Production Scale · Price: ~$1,200–$2,500/mo base · Inclusions: Unlimited input formats, unified forecasting endpoints, processing for up to 5M events per month, and standard technical support.
- Name: High-Volume Hub · Price: ~$30k–$45k/yr · Inclusions: Dedicated throughput pipelines, custom EDI ingestion mapping design, priority SLA uptime, and unlimited event streaming.
**Guarantee**: Guarantees sub-second normalization of inbound telemetry; if processing latency exceeds the SLA for more than 0.1% of events in a given billing cycle, the subsequent month's base fee is credited.
**Business Function**: ProvideService
**Objection Handlers**:
- We rely on legacy EDI, not modern APIs -> Depotridge is engineered to poll legacy EDI and flat files at high frequency, generating a normalized real-time stream.
- We already use Project44 -> Project44 focuses on over-the-road transit visibility; Depotridge specifically unifies fragmented yard and dock telemetry directly at the destination facility.
- Data normalization at high volume is error-prone -> The platform utilizes strict schema validation on ingestion to quarantine anomalies without halting the primary forecast stream.
**Pricing Architecture**: MeteredStreaming
**Agent Checkout Support**:
- agentic-commerce-protocol

## Startup Brand

**Voice**: Pragmatic supply chain register anchored by absolute technical precision
**Tagline**: Turn fragmented warehouse telemetry into real-time inbound forecasts
**Icon Concept**: pallet
**Palette Intent**: industrial-safety
**Visual Identity**: The visual identity contrasts matte concrete grays with high-visibility safety orange, employing rigid grid typography that evokes active loading docks.
**Archetype Reference**: the-ruler

## Startup Buyer Chain

**Chain**: B2B: Depotridge → Logistics Data Engineers → Supply Chain Operations Directors
**Gtm Motion**: Acquires initial usage by providing self-serve API access to logistics data teams attempting to normalize telemetry for a single high-volume distribution center. Expands contract value by scaling node coverage across the customer's broader regional warehouse network and integrating upstream supplier logistics feeds.
**Agent Channel**: Designed to list in the LangChain tool registry and Microsoft Copilot ecosystem as a native telemetry aggregator endpoint for supply chain forecasting agents.
**Primary Channel**: Direct technical search and capability listings on AWS Data Exchange for engineering queries like 'real-time warehouse telemetry API' or 'programmatic EDI aggregator'.

## Startup Customer Journey

```mermaid
flowchart LR; A[AWS Data Exchange] --> B[Developer Stream API]; B --> C[Distribution Center]; C --> D[Telemetry Normalization Engine]; D --> E[Regional Warehouse Network]; E --> F[High-Volume Hub Pipeline]; F --> G[Automated Sorting Facilities];
```

## Startup Proof Points

_Illustrative — target and order-of-magnitude estimate figures, not an achieved track record (this Thing is concept-stage)._

**Pilot Goals**:
- 30-day single-facility ingestion pilot: Aiming to successfully poll and normalize legacy EDI and flat files from three distinct sources into a unified API endpoint with sub-second latency.
- 60-day high-volume sorting pilot: Targeting the continuous processing of up to 5M monthly telemetry events while maintaining >99.9% mapping accuracy and zero primary stream interruptions.
**Target Metrics**:
- Target: >99.9% mapping accuracy across fragmented legacy EDI payloads.
- Aim: 30% reduction in dock scheduling conflicts.
- Target: <1 second normalization latency for inbound yard and dock telemetry.
- Aim: 0 downtime events caused by anomalous data, validated by active schema quarantines.
**Target Case Studies**:
- Regional 3PL Operations Director: Transitioning a multi-facility network from batch-processed legacy EDI to real-time streaming, targeting a measurable reduction in daily dock scheduling conflicts.
- Enterprise Automated Sorting Facility Manager: Replacing delayed flat-file ingestion with sub-second API normalization, aiming to eliminate batch-processing pauses and unify inbound telemetry.
- Logistics IT Leader at a Legacy Distribution Center: Mapping three fragmented legacy WMS payloads into a single streaming endpoint, targeting complete schema validation without requiring a core system overhaul.
**Testimonial Targets**:
- VP of Logistics: Expressing relief that fragmented EDI and flat-file data finally flows into a single, real-time forecast stream without requiring a massive IT migration.
- Yard Management Director: Validating that sub-second data normalization directly eliminates the blind spots between over-the-road transit and destination facility sorting.
- Logistics IT Manager: Praising the strict schema validation that automatically quarantines anomalies without halting the entire high-volume forecast pipeline.

## Startup Top Risks

**Risks**:
- Severity: existential · Description: Major Warehouse Management Systems like Manhattan Associates or Blue Yonder block or severely rate-limit third-party API access to the telemetry data required for forecasting. · Mitigation Status: in-progress
- Severity: high · Description: Large enterprise customers refuse to replace entrenched Project44 or EDI contracts due to the high switching costs associated with ripping out legacy ERP integrations. · Mitigation Status: unmitigated
- Severity: moderate · Description: Real-time streaming infrastructure struggles to process and normalize highly corrupted legacy EDI feeds without introducing the very batch delays Depotridge claims to eliminate. · Mitigation Status: in-progress
- Severity: low · Description: Hardware sensor variance across different third-party logistics providers creates edge cases that temporarily break the unified inbound forecasting models. · Mitigation Status: mitigated

## Startup Competitors

- [Manual Spreadsheet Reconciliation](/Competitors/Manual_Spreadsheet_Reconciliation) — Status Quo
- [Legacy EDI Aggregators](/Competitors/Legacy_EDI_Aggregators) — Incumbent
- [Project44](/Competitors/Project44) — Visibility Platform
- [FourKites Supply Chain](/Competitors/FourKites_Supply_Chain) — Visibility Platform
- [Descartes MacroPoint](/Competitors/Descartes_MacroPoint) — Incumbent

## Startup Solution Stack

- [Inbound Forecast Service](/Services/Inbound_Forecast_Service) — Service-as-Software
- [Stream Reconciliation Worker](/Agents/Stream_Reconciliation_Worker) — Agent
- [Telemetry Normalization Engine](/Software/Telemetry_Normalization_Engine) — Software
- [Warehouse Integration API](/Software/Warehouse_Integration_API) — Software

## Startup Story Brand

**Hero**:
- **Need**: to be the operational architect who eliminates dock congestion through data-driven precision
- **Want**: to convert fragmented warehouse telemetry into unified, real-time inbound forecasts
- **Identity**: the logistics director at a high-volume regional 3PL facility
**Plan**:
- Step: Submit · Detail: Provide your legacy EDI or telemetry endpoints for initial schema mapping and quarantine validation.
- Step: Confirm · Detail: Verify the normalized stream output to ensure 99.9% mapping accuracy across your inbound freight.
- Step: Stream · Detail: Redirect the unified forecast data into your existing dock management or sorting facility systems.
**Guide**:
- **Empathy**: Dock throughput records are won in minutes — but the reality of fragmented telemetry makes every shift a scramble.
**Problem**:
- **Villain**: legacy EDI latency
- **External**: Inbound scheduling depends on manual spreadsheet reconciliation of batch-processed flat files and delayed EDI status updates.
- **Internal**: You feel like you are guessing at dock capacity while hardware sits idle.
- **Philosophical**: Every logistics leader deserves immediate visibility into their own yard — not batch-processed summaries of yesterday's failures.
**Success**: Dock managers operate from a single, live truth, enabling sub-second adjustments to inbound schedules and eliminated sorting delays.
**One Liner**: Instead of manual spreadsheet reconciliation, Depotridge normalizes fragmented warehouse telemetry into real-time inbound forecasts — eliminating dock scheduling conflicts.
**Positioning**:
- **So That**: unify fragmented yard and dock data for real-time forecasting
- **Unlike**: Legacy EDI aggregators
- **For Whom**: logistics directors at regional 3PL hubs
- **Category**: Telemetry normalization for 3PL facilities
**Call To Action**:
- **Direct**: Provision API Stream
- **Transitional**: Download Schema Validator
**Failure Stakes**:
- Compounding dock scheduling conflicts
- Idle automated sorting equipment
- Unnecessary labor overtime costs
**Transformation**:
- **To**: one of the few logistics directors who controls real-time yard telemetry
- **From**: the manager reacting to batch-processed EDI spreadsheets
**Controlling Idea**: Real-time inbound visibility is a requirement for modern dock efficiency.

## Startup Landing Hero

**Eyebrow**: 3PL Data Normalization Platform
**Headline**: Control your dock with real-time inbound telemetry
**Supporting Proof**: Sub-second normalization of legacy EDI and raw sensor streams

## Startup Landing Hero Services

**Eyebrow**: 3PL telemetry normalization
**Headline**: Real-time inbound forecasts from fragmented warehouse telemetry

## Startup Landing Hero Headless Saa S

**Eyebrow**: Warehouse telemetry API
**Headline**: Turn legacy EDI into real-time forecast streams
**Supporting Proof**: Ingests standard EDI and flat file schemas

## Startup Landing Problem

**Cards**:
- Body: Logistics teams spend hours manually merging flat files and Excel exports to estimate arrival times. By the time the data is cleaned, the physical trucks are already backed up at the gate, rendering the forecast obsolete before it hits the floor. · Heading: Batch-processed spreadsheet reconciliation
- Body: Schedulers click through individual carrier websites to verify load positions because the central EDI feed lags by hours. This fragmented hunting and pecking prevents a unified view of the yard, leading to idle sorting equipment and misallocated labor. · Heading: Polling carrier portals for status updates
- Body: Without live telemetry, directors default to staffing for peak volume every shift. When inbound freight arrives late or out of sequence, you pay for expensive overtime and idle warehouse hours that could have been avoided with precise, real-time arrival windows. · Heading: Over-scheduling labor for 'just in case' coverage
**Section Heading**: Legacy EDI latency forces you to manage docks by guesswork

## Startup Landing Solution

**Section Heading**: Command your dock with unified warehouse telemetry streams
**Solution Statement**: Depotridge is a telemetry normalization engine for 3PL facilities. It is designed to ingest raw EDI flat files and asynchronous sensor data, mapping them into a single, high-speed forecast stream compatible with WMS platforms like Blue Yonder or SAP.

## Startup Landing Features

**Benefits**:
- Detail: Our engine polls legacy systems at high frequency to generate a normalized stream without manual data entry. · Benefit: Eliminate manual spreadsheet reconciliation of EDI data · Feature: automated telemetry normalization engine for fragmented flat files and batch-processed EDI status updates · Icon Name: FileJson
- Detail: Shift from reacting to yesterday's failures to making real-time adjustments as freight enters the yard. · Benefit: Prevent dock congestion using live yard visibility · Feature: sub-second normalization of inbound telemetry events into a unified forecast service · Icon Name: Activity
- Detail: Eliminate idle hardware by aligning sorting schedules with precise, real-time arrival telemetry. · Benefit: Keep automated sorting equipment running at capacity · Feature: stream reconciliation workers that redirect unified data directly into existing facility systems · Icon Name: Cpu
- Detail: Maintain 99.9% mapping accuracy across fragmented legacy schemas and diverse WMS formats. · Benefit: Protect data integrity with automated schema validation · Feature: strict quarantine validation on ingestion to isolate anomalies without halting primary forecasts · Icon Name: ShieldCheck
- Detail: Avoid labor spikes by matching shift staffing to actual inbound volume instead of batch estimates. · Benefit: Reduce labor overtime through precise scheduling · Feature: warehouse integration API providing real-time inbound streams for dock manager decision support · Icon Name: Clock
**Section Heading**: Convert fragmented warehouse telemetry into unified inbound forecasts in real-time

## Startup Landing Social Proof

_Illustrative — target and order-of-magnitude estimate figures, not an achieved track record (this Thing is concept-stage)._

**Section Heading**: Engineered for high-volume 3PL telemetry and dock precision
**Capability Claims**:
- Normalizes fragmented legacy EDI and flat-file payloads into a single real-time forecast stream.
- Maintains sub-second normalization latency for inbound yard and dock telemetry events.
- Validates and maps legacy schemas with 99.9% accuracy to eliminate manual reconciliation.
- Quarantines anomalous data automatically via strict schema validation without halting primary streams.
**Foundation Signals**:
- Built for high-volume ingestion of legacy EDI, flat files, and WMS payloads.
- Utilizes sub-second latency pipelines for automated sorting facility integration.
- Secure API streaming and schema mapping for regional distribution center standards.

## Startup Landing Pricing

_Illustrative — target and order-of-magnitude estimate figures, not an achieved track record (this Thing is concept-stage)._

**Tiers**:
- Name: Developer Stream · Price: ~$0.01–$0.03 per ingested event · Tagline: For logistics engineers prototyping unified yard telemetry and WMS mapping. · Cta Label: Start with API · Highlighted: false
- Name: Production Scale · Price: ~$1,200–$2,500/mo base · Tagline: For regional hubs requiring unified forecasting and live dock scheduling. · Cta Label: Provision API Stream · Highlighted: true
- Name: High-Volume Hub · Price: ~$30k–$45k/yr · Tagline: For enterprise 3PL facilities needing dedicated throughput and custom mapping. · Cta Label: Connect Data · Highlighted: false
**Billing Note**: Metered-streaming pricing — illustrative bands shown until live. Volume discounts apply.
**Section Heading**: Real-time Visibility Built for Your Facility

## Startup Landing Faq

**Faqs**:
- Answer: Depotridge acts as a high-frequency polling engine for legacy EDI and flat files. The system continuously ingest these static formats and converts them into a normalized, real-time stream that your modern dock management tools can consume immediately. · Question: Our facility relies on legacy EDI and flat files rather than modern APIs.
- Answer: Those platforms track over-the-road transit between points. Depotridge focuses exclusively on the 'black hole' of the destination facility, unifying fragmented yard telemetry and dock sensors into a single forecast so you can manage local congestion. · Question: How is this different from tracking platforms like Project44 or FourKites?
- Answer: The system applies strict schema validation at the point of ingestion. This allows the platform to quarantine malformed data or anomalies into a separate validation queue without interrupting the primary forecast stream, maintaining 99.9% mapping accuracy. · Question: Is high-volume data normalization reliable enough for automated sorting?
- Answer: We guarantee sub-second normalization of inbound telemetry. If processing latency exceeds our SLA for more than 0.1% of events in any billing cycle, we credit the entire base fee for your subsequent month of service automatically. · Question: What happens if the stream lags while we are managing a high-volume shift?
- Answer: Initial schema mapping and quarantine validation typically occur within the first 48 hours of providing your telemetry endpoints. You can verify the normalized output against your raw data during the 'Confirm' phase before redirecting the stream to your production systems. · Question: How long does it take to map our specific warehouse management schemas?
**Section Heading**: Common Questions and Technical Objections

## Startup Token Hero

**Genre**: founding-hypothesis
**Rendered**: Instead of manual spreadsheet reconciliation, Depotridge normalizes fragmented warehouse telemetry into real-time inbound forecasts — eliminating dock scheduling conflicts.
**Mechanism**: spine-derived-v1
**Template Id**: spine-founding-hypothesis
**Vocab Fingerprint**: 81e22ac9fcea3dbe

## Startup Token Positioning

**Genre**: moore-positioning
**Rendered**: Telemetry normalization for 3PL facilities for logistics directors at regional 3PL hubs. Unlike Legacy EDI aggregators — unify fragmented yard and dock data for real-time forecasting.
**Mechanism**: spine-derived-v1
**Template Id**: spine-moore-positioning
**Vocab Fingerprint**: 75492b42a116d459

## Startup Token Pitch Deck

**Genre**: pitch-deck
**Rendered**: Problem: Inbound scheduling depends on manual spreadsheet reconciliation of batch-processed flat files and delayed EDI status updates.
Solution: Instead of manual spreadsheet reconciliation, Depotridge normalizes fragmented warehouse telemetry into real-time inbound forecasts — eliminating dock scheduling conflicts.
Customer: logistics directors at regional 3PL hubs
Unlike: Legacy EDI aggregators
**Mechanism**: spine-derived-v1
**Template Id**: spine-pitch-deck
**Vocab Fingerprint**: 110c08c9311426cd

## Startup Token M E D D P I C C

**Pain**: Inbound scheduling depends on manual spreadsheet reconciliation of batch-processed flat files and delayed EDI status updates.
**Metrics**: Target: Dock managers operate from a single, live truth, enabling sub-second adjustments to inbound schedules and eliminated sorting delays.
**Rendered**: Pain: Inbound scheduling depends on manual spreadsheet reconciliation of batch-processed flat files and delayed EDI status updates.
Economic buyer: Logistics Data Engineers
Metrics: Target: Dock managers operate from a single, live truth, enabling sub-second adjustments to inbound schedules and eliminated sorting delays.
Competition: Legacy EDI aggregators
**Mechanism**: spine-derived-v1
**Competition**: Legacy EDI aggregators
**Economic Buyer**: Logistics Data Engineers
**Vocab Fingerprint**: aa205563bc42896a

## Startup Token Cold Email

**Genre**: cold-email
**Rendered**: Subject: Telemetry normalization for 3PL facilities for logistics directors at regional 3PL hubs

logistics directors at regional 3PL hubs — Inbound scheduling depends on manual spreadsheet reconciliation of batch-processed flat files and delayed EDI status updates. Instead of manual spreadsheet reconciliation, Depotridge normalizes fragmented warehouse telemetry into real-time inbound forecasts — eliminating dock scheduling conflicts.
**Mechanism**: spine-derived-v1
**Template Id**: spine-cold-email
**Vocab Fingerprint**: 6f98328989b0a75c

## Startup Token Agent Spec

**Genre**: ai-agent-spec
**Rendered**: Telemetry normalization for 3PL facilities. Instead of manual spreadsheet reconciliation, Depotridge normalizes fragmented warehouse telemetry into real-time inbound forecasts — eliminating dock scheduling conflicts. Serves logistics directors at regional 3PL hubs.
**Mechanism**: spine-derived-v1
**Template Id**: spine-ai-agent-spec
**Vocab Fingerprint**: f9c2e9d1cd4babef

## Neighborhood

### Candidate solutions

- [Manage Idle Inventory Costs](/Problems/Manage_Idle_Inventory_Costs) — candidate solution for · Problems
- [Cross-Dock Throughput Bottlenecks](/Problems/Cross-Dock_Throughput_Bottlenecks) — candidate solution for · Problems

### Composed of

- [Warehouse Integration API](/Software/Warehouse_Integration_API) — composes · Software
- [Inbound Forecast Service](/Services/Inbound_Forecast_Service) — composes · Services
- [Stream Reconciliation Worker](/Agents/Stream_Reconciliation_Worker) — composes · Agents
- [Telemetry Normalization Engine](/Software/Telemetry_Normalization_Engine) — composes · Software

### What it offers

- [Inbound Telemetry Stream](/Software/Inbound_Telemetry_Stream) — offers · Software

### Embodies

- [Software](/Theses/Software) — embodies · Theses

### Competitors

- [Project44](/Competitors/Project44) — competes with · Competitors
- [FourKites Supply Chain](/Competitors/FourKites_Supply_Chain) — competes with · Competitors
- [Descartes MacroPoint](/Competitors/Descartes_MacroPoint) — competes with · Competitors
- [Manual Spreadsheet Reconciliation](/Competitors/Manual_Spreadsheet_Reconciliation) — competes with · Competitors
- [Legacy EDI Aggregators](/Competitors/Legacy_EDI_Aggregators) — competes with · Competitors

### Similar Startups

- [Autarrival](/Startups/Autarrival) — similar · Startups
- [Cargovista](/Startups/Cargovista) — similar · Startups
- [Cornerstonedock](/Startups/Cornerstonedock) — similar · Startups
- [Congestionyard](/Startups/Congestionyard) — similar · Startups
- [Floorfuel](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Floorfuel) — similar · Startups
- [Chord](/CompanyTypes/Tier_1_National_Shingle_Brands/Problems/Distributor_Inventory_Blindspots/Startups/Chord) — similar · Startups
- [Spottercenter](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Spottercenter) — similar · Startups
- [Autopilotdock](/Startups/Autopilotdock) — similar · Startups
- [Cadencesurge](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Cadencesurge) — similar · Startups
- [Conveyorbond](/Startups/Conveyorbond) — similar · Startups
- [Warehousebase](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Warehousebase) — similar · Startups
- [Warehouseray](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Warehouseray) — similar · Startups
- [Arrivalguild](/Startups/Arrivalguild) — similar · Startups
- [Wholesalequay](/Startups/Wholesalequay) — similar · Startups
- [Coordinatorfoundry](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Coordinatorfoundry) — similar · Startups
- [Autowarehouse](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Autowarehouse) — similar · Startups
- [Gleamharbor](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Gleamharbor) — similar · Startups
- [Directorguild](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Directorguild) — similar · Startups
- [Fuserange](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Fuserange) — similar · Startups
- [Codeshade](/CompanyTypes/Large-Scale_3PL_&_Cross-Docking_Hub/Problems/Cross-Dock_Throughput_Bottlenecks/Startups/Codeshade) — similar · Startups