Strategic acquisition opportunity

Acquire a built AI video-clipping platform.

Clipper.mov turns long-form video into short vertical clips. It transcribes a recording, scores every moment for short-form potential, explains why it chose each one, and renders captioned 9:16 output. The web platform, processing pipeline, iOS application and subscription infrastructure are already built.

It is pre-revenue with no active user base. What is on offer is the engineering, the product design and the commercial infrastructure — not traction.

Request acquisition information Run the product yourself

The product works today.

These are unedited clips produced by the live pipeline from public-domain source footage — captions burned in, each scored with the model's own reasoning. The same pipeline runs for any uploaded video.

Astronaut's First Spaceflight

A personal first-spaceflight story creates an emotional connection that keeps viewers watching.

Total Solar Eclipse Explained

Opens on a rare, high-curiosity astronomical event — a strong hook for the first 3 seconds.

Meet the Lunar Rover Viper

Introduces a novel piece of technology with a clear payoff — high shareability for tech audiences.

Built, not designed.

Figures measured directly from the repository, excluding dependencies and generated code.

~19,600

lines of first-party TypeScript

306

source files across web, worker and mobile

API routes (101 handlers)

web pages

iOS screens

database models

Built technology

Three deployable units: a Next.js application, a containerised media worker, and a React Native client, over shared Postgres and object storage.

Clients

Web app · iOS app

Next.js API

77 routes · auth · quotas · billing

Queue

Signed job dispatch + callbacks

Media worker

FFmpeg · Whisper · GPT · OpenCV

Storage & data

Postgres (Prisma) · object storage

Web application

Next.js 15 (App Router), React 19, TypeScript, Tailwind. Deployed on Vercel.

Data

PostgreSQL via Prisma — 29 models covering projects, videos, clips, jobs, scheduling, agency workspaces, usage and billing.

Auth & storage

Supabase authentication and object storage; server-signed uploads so clients never hold storage credentials.

Processing worker

Containerised Node + FFmpeg service on Fly.io: source acquisition, transcode, 9:16 reframe, caption burn-in, clip render.

Whisper transcription with word-level timestamps; GPT analysis that scores moments and returns a written rationale per clip; OpenCV face detection for subject-centred reframing.

Payments

Stripe subscriptions and billing portal on web; RevenueCat with StoreKit 2 for iOS in-app purchases.

Mobile

React Native / Expo (SDK 52) iOS application sharing the web backend. Android package configured, not yet built.

Integrations

Google Drive, Dropbox, OneDrive, Slack and YouTube OAuth connectors; Resend for transactional email.

Operations

Admin surface for users, queues, incidents, reports and feature flags; rate limiting; health checks; workflow automation engine.

What the buyer acquires

Subject to definitive agreement and due diligence.

Brand and domain

The Clipper.mov name, identity and the clipper.mov domain.

Web platform

The full Next.js application — marketing site, authenticated product, admin surface and public interactive demo.

iOS application

The React Native application and its App Store Connect record (App ID 6797315332), bundle identifier com.clipper.mov.

Processing pipeline

The containerised worker: transcription, moment selection, reframing, caption rendering and clip export.

Backend and schema

77 API routes and the Prisma schema, including the agency/client workspace model.

Monetization infrastructure

Stripe subscription plumbing, plan and quota definitions, credit metering, and RevenueCat IAP configuration.

Integrations

Implemented OAuth connectors for Google Drive, Dropbox, OneDrive, Slack and YouTube.

Demo assets

Public-domain source material and the rendered example clips used across the site and demo.

Commercial infrastructure

The billing system is built and the plan structure is defined. It has not yet been sold into a market — there is no revenue and no subscriber base.

Subscriptions

Stripe checkout, billing portal, webhook handling, and four defined tiers with per-plan upload, credit, clip and duration limits enforced server-side.

In-app purchase

RevenueCat with StoreKit 2 configured for iOS, with the paywall, restore flow and auto-renewal disclosures implemented.

Usage metering

Processing credits are metered per video and per billing period, with quota checks before a job is accepted.

Distribution

In place

Public marketing site with use-case pages and an interactive demo requiring no account
App Store Connect record prepared for iOS distribution

Potential

Organic search against a well-defined, high-intent category
Agency and creator partnerships, supported by the existing client-workspace model
Bundling into an acquirer's existing customer base

Where it could go next

Each item is an opportunity, not an existing capability.

Transcript layer

Transcription already runs with word-level timing but is discarded. Retaining it enables search, transcript editing and caption correction.

Multi-platform publishing

YouTube publishing exists; the scheduling model and connector pattern are in place for further platforms.

API and white-label

A versioned /api/v1 surface and an agency workspace model already exist to build on.

Android

The React Native codebase is shared; the Android package is configured but unbuilt.

Why acquire rather than build

The hard part of this category is not the interface — it is the media pipeline and the judgement layer on top of it. Both exist and run.

Media pipeline

Transcode, reframe, caption burn-in and export, with per-stage fallbacks

Transcription

Word-level timing, driving both captions and moment selection

Moment selection

Scoring with a written rationale per clip

Subject tracking

Face detection for subject-centred vertical crops

Billing and quotas

Subscriptions, credit metering and server-side enforcement

Two clients

Web application and iOS application over one backend

Who could take it further

Creator-tools companies

An existing creator audience to distribute into, where clipping is a natural adjacent feature.

Video and media platforms

Hosting, streaming or podcast businesses whose customers already hold long-form libraries.

Marketing and social SaaS

Scheduling and social-management products that lack a production step before publishing.

Agencies and agency networks

The client-workspace and approval model was built for delivering to multiple clients.

AI and infrastructure companies

An applied, revenue-ready surface on top of transcription and inference capability.

Strategic investors

A built platform to fund and commercialise rather than a concept to finance.

Current platform status

Stated plainly, including what is unfinished. Anything below would surface in diligence regardless.

Built and running

Web application live at clipper.mov
Processing pipeline operational end to end — upload, transcription, moment selection, captioned 9:16 render
Stripe subscription infrastructure and plan/quota enforcement
Supabase authentication, storage and server-signed uploads
Public interactive demo running on real pipeline output
Admin surface, rate limiting, health checks and transactional email

Built, pending configuration or release

iOS application — complete and functional; first submission was rejected under App Store Guideline 5.6 and it is currently being remediated, not yet released
Android — package configured, application not yet built
Watermarking and poster-frame generation — implemented, awaiting a worker deployment
Publishing — YouTube implemented; TikTok, Reels and LinkedIn are not built

Not present

Revenue — the product is pre-revenue
Users — there is no active user base
Transcript storage — transcription runs but the transcript is not retained

Acquisition and due diligence

Qualified parties can request a product demonstration, technical architecture, source-code review, database schema, API documentation, monetization detail and deployment documentation. Confidential material is shared under NDA rather than published here.