AI SaaS case study

Alpha Drafts

Two jobs in one app: write the document, then ask the document questions. Both metered on credits, both ending in a PDF.

Alpha Drafts: AI SaaS
  • IndustryWriting and productivity SaaS
  • UsersStudents, professionals and academics
  • DeliveredSeptember 2024
  • ServicesProduct Design, Development, AI

Overview

Alpha Drafts writes long-form work to a brief — subject, length, formatting style, whether it needs citations — and hands back an editable draft rather than a wall of chat. When the draft is right, it exports as a PDF.

The other half runs the same relationship backwards. Upload a PDF and ask it questions: what does this say about X, where is the figure, summarise section three. The document stays on screen beside the conversation, so an answer can be checked against the page it came from.

Everything is metered on credits against a daily allowance, with three plans behind it — which is the part that turned a demo into a product.

  • AI SaaS
  • GPT-4
  • Content Generation
  • PDF Chat
  • Rich Text Editor
  • PDF Export
  • Credit Billing

Project video

Content that writes itself.
YouTube

The drafting flow, the PDF conversation and the credit model behind both.

Key capabilities

  • A brief, not a prompt

    Type of piece, length, formatting style and citation handling are fields — so the person writing does not have to know how to ask.

  • The draft lands in an editor

    Headings, emphasis, lists and alignment, in place. The output is a document being worked on rather than a message to copy out.

  • Chat with a PDF you uploaded

    Ask a document what it says, with the page open beside the answer so it can be checked rather than trusted.

  • Credits, visible at all times

    A daily allowance in the header of every screen. Nobody discovers the limit by hitting it.

A chat box will write an essay, and then the work starts: it is the wrong length, the citation style is not the one required, the formatting has to be rebuilt somewhere else, and turning it into a file to submit is a manual job every single time. The gap between "a model can write this" and "I have a finished document" is where the effort actually goes, and it is a gap made of small, repetitive, unglamorous steps.

  • A chat transcript is not a document

    Formatting is lost on the way out, and rebuilding it in a word processor undoes most of the time saved.

  • The requirements come as an afterthought

    Length, style and citations are decided before writing, and a prompt box asks for them last, if at all.

  • Usage nobody can see is usage nobody can budget

    Unmetered AI is either a bill that surprises the operator or a limit that surprises the user.

Questions

Long-form work to a brief — essays and papers are what it was built around, and the same fields cover reports, emails and articles. The formatting style and citation handling are part of the request rather than something to fix afterwards.

Got a model and no product around it?

Let's build the part people pay for.