Productized sites for churches that still fax

A constrained website kit: service times, sermon audio, donation, calendar. One intake form. Ships in a week. Not a generic page builder.

For Small churches whose site is a 2009 Frontpage leftover

Riff on @T_Zahil — productized service, not another CMS

The problem, sharper

Small churches whose site is a 2009 Frontpage leftover already tried the generic version and bounced. A constrained website kit: service times, sermon audio, donation, calendar. One intake form. Ships in a week. Not a generic page builder. The wedge is the constraint, not another feature list.

Features that make the pitch true

01Capture the job in one screen: A constrained website kit: service times, sermon audio, donation, calendar. One intake…
02Audience-aware defaults for small churches whose site is a 2009 frontpage leftover.
03Shareable artifact you can send to a teammate in one tap.
04Honest empty states. No fake social proof, no infinite onboarding.
05Export: the user can leave with their data on day one.

This weekend

Friday: landing page, one happy path, seed data.
Saturday: the core loop that makes the pitch true.
Sunday: share link, ugly-but-working export, tell ten people.

Stack

— Next.js + TypeScript
— Local-first persistence, server later
— city search
— availability calendar
— SMS confirmations
— role-based access

User stories

As a person in this group: Small churches whose site is a 2009 Frontpage leftover, I can describe the job in one sentence and get a usable first result.
As a skeptic, I can try it without creating an account.
As someone who might build this, I can copy a spec and start this weekend.

Paste into Cursor, Claude Code, or Codex

Build a working product called OrchardKit.

Tagline: Productized sites for churches that still fax — without the usual product theater.

One-liner: A constrained website kit: service times, sermon audio, donation, calendar. One intake form. Ships in a week. Not a generic page builder.

Who it is for: Small churches whose site is a 2009 Frontpage leftover

Non-goals: do not build a generic local app. Do not add auth until the core loop works. Do not invent extra personas.

Must-have features:
1. Capture the job in one screen: A constrained website kit: service times, sermon audio, donation, calendar. One intake…
2. Audience-aware defaults for small churches whose site is a 2009 frontpage leftover.
3. Shareable artifact you can send to a teammate in one tap.
4. Honest empty states. No fake social proof, no infinite onboarding.
5. Export: the user can leave with their data on day one.

Suggested stack:
- Next.js + TypeScript
- Local-first persistence, server later
- city search
- availability calendar
- SMS confirmations
- role-based access

UX:
- Distinctive, editorial, not purple-gradient SaaS
- Works on a phone
- Empty states teach the product
- One primary action per screen

Ship this weekend:
1. A landing page that states the job in one breath
2. The core loop end to end with sample data
3. A shareable output
4. A README that explains what was intentionally left out

Constraints: TypeScript. Keep the first version local-first if a database would slow you down. Name the product OrchardKit unless you have a clearly better one.