Internal Tool Replacement

3 weeks

Oct 2025

Media Production

Creating ScribeKit: From $10K+ in SaaS Costs to Under $2 per Project

Podcast Production Agency

Cost Reduction

From $10K+/year to <$2/project

Eliminated recurring SaaS fees and pay-per-credit pricing

Team Collaboration

100% improvement

Shared workspace replaced shared logins to the same account

Feature Control

Full ownership

Foundation for custom features built to their exact workflow

The Problem

A podcast production agency produces high-quality podcasts for clients across multiple industries. Their workflow required accurate transcription for:

  • Client review and approval
  • Editor reference during post-production
  • Show notes and content creation
  • Accessibility and SEO

They were paying thousands annually for transcription software that:

  • Charged per user, per month (limited team scaling)
  • Required purchasing credits in bulk ($1000+ annually in transcription credits)
  • Offered limited collaboration (editors worked in isolation)
  • Locked them into rigid export formats
  • Couldn't be customized for their specific client needs

Every new team member meant another seat license. Every project consumed expensive credits. The tool worked, but it was built for everyone, which meant it was perfect for no one.

The Solution: ScribeKit

We built ScribeKit, a custom internal tool designed specifically for their podcast production workflow.

Screenshot 1

Upload audio or video files and start transcription with automatic speaker diarization.

Screenshot 2

View and manage all transcriptions in a centralized workspace with status tracking.

Screenshot 3

Role-based access control with admin and editor permissions for team collaboration.

Screenshot 4

Collaborative editing interface with real-time transcript updates and media playback.

Core Features

User Management & Roles:

  • Admin users: Full system control, user management, project oversight
  • Editor users: Project access, transcription editing, client deliverables
  • Role-based permissions matched their actual team structure

Audio/Video Upload & Transcription:

  • Drag-and-drop upload for audio or video files
  • Automatic transcription using AI (AssemblyAI API)
  • Speaker diarization to automatically identify and label different speakers
  • Processing status tracking with estimated completion times

Collaborative Editing Interface:

  • Real-time text editing of transcriptions
  • Bulk speaker renaming (change "Speaker A" across entire transcript)
  • Timestamp synchronization with original audio
  • Comment and annotation system for editor notes
  • Shared workspace for team collaboration
  • Media playback with transcripts that auto-follows for editing

Multiple Export Formats:

  • Client proof format (clean, formatted for review)
  • Editor reference format (timestamps, speaker labels)
  • Show notes template (optimized for content creation)
  • Custom export formats tailored to specific client needs
  • Batch export for multiple episodes

Technical Architecture

Built as a modern web application:

  • Next.js for server-side rendering and API routes
  • React for interactive editing interface
  • Tailwind CSS for responsive, professional design
  • AssemblyAI API for AI-powered transcription and diarization
  • Vercel deployment (low-cost hosting, scales automatically)

The entire codebase was handed over to the client. They own it completely.

The Results

Cost Transformation

Before ScribeKit:

  • Software licenses: $150/month per user × 6 users = $900/month
  • Transcription credits: $1,000-2,000 annually (bulk purchases)
  • Annual cost: $12,000-13,000

After ScribeKit:

  • One-time development: $15,000
  • Transcription API costs: ~$1.50 per hour of audio
  • Hosting: Free tier (Vercel)
  • Per-project cost: under $2 (most podcasts are 30-60 minutes)

Payback period: 13 months. After that, pure savings.

Operational Improvements

Team Collaboration: Editors now work in a shared workspace instead of isolated individual accounts. They can see each other's progress, share annotations, and collaborate on complex episodes. The tool scales perfectly. Hiring new team members costs nothing.

Customization Freedom: They can now build custom features exactly matching their workflow. Need a client-specific export format? Add it. Want integration with their project management system? Build it. They own the code.

Client Experience: Custom export formats mean clients receive transcripts formatted exactly how they need them. No more reformatting in Word. Deliverables look professional and consistent across all projects.

What Made This Work

Focused Scope: We didn't try to build a general-purpose transcription platform. ScribeKit solves one specific workflow for one specific type of team. That focus meant we could build it in 3 weeks instead of 6 months.

Workflow-First Design: We started by mapping their actual process. Where did work get stuck? What took too long? What required too many manual steps? The tool was built around their workflow, not forcing them to adapt to generic software.

Progressive Ownership:

  • Week 1: Workflow mapping and design
  • Week 2-3: Development and integration
  • Week 4: Testing with their actual team and projects
  • Handoff: Complete codebase, documentation, and hosting setup

They were involved throughout. By the time we handed over the code, they already knew how it worked because they'd been using it with real projects.

The Business Impact

This project paid for itself in saved SaaS costs within 13 months.

But the real value isn't just cost savings. It's:

  • Control: They can modify the tool as their business evolves
  • Scalability: No per-seat pricing means they can grow without software costs increasing
  • Competitive advantage: Custom features their competitors using off-the-shelf tools can't match
  • Foundation for innovation: They can now build additional workflow tools on the same foundation - optimising more of their custom workflow

Lessons for Other Teams

This pattern works when:

  • You're paying for 80% of features you don't use
  • Per-seat pricing punishes you for growing your team
  • You need 3-4 different tools to accomplish one workflow
  • Your process is stable enough to build around
  • The cost of customization is lower than ongoing SaaS fees

This isn't for every scenario: If your workflow changes every month, you might not be ready for custom tools. If you need 100+ integrations with other platforms, off-the-shelf tools might make more sense.

But if you're an operations team, agency, or service business with established workflows and growing SaaS costs, custom internal tools can fundamentally change your economics.

ScribeKit represents a typical Clearly Design internal tools project: 3-4 weeks of development, $12-20K investment, complete code ownership, and economics that make sense within the first year.

Want to explore custom tools for your team? Schedule a workflow audit call to see if internal tool replacement makes sense for your business.

Ready to replace your SaaS stack?

Let's map your workflow and identify where custom tools could save you thousands annually while giving you full control.