WORKSITEby CityTree

Operations software for churches

Church software fails because it asks volunteers to log in. Worksite goes to them.

The work reaches people where they already are: email and text. Every message carries one link to one page that does one thing. Check the job off, sign the form, claim the Saturday shift. No account, no password, no app.

Built inside a working church by someone who has served in one for many years. We set it up, connect your tools and host it for you.

Worksite's one-job page on a phone: Paint the trim in the youth room, with a note box, a photo button and a green Mark it done button.
What Jordan sees. He never made an account.

The design brief

Teams, Slack, Asana and a shared drive all failed the same way. People forgot their passwords, and nobody remembered to go and check.

There will be some volunteers that never log into Worksite, and interact with it solely through their email or the messages that come to them.

That sentence came first. Everything in Worksite was built around it.

How it reaches people

The man who mends the gate won't learn an app. He'll read a text.

STEP 1

A message arrives

The office assigns a job, even to someone with no account. It goes out by email or text, in plain words, with one link.

Still able to do this one? Set up 300 chairs on the field, Saturday from 2pm.
Text · 8:02am
STEP 2

One page, one job

The link opens a page that shows that one job and nothing else. Add a note or a photo of the mended gate, then press the button.

Mark it done
Nothing to sign in to. This link is yours and shows this one job.
STEP 3

The office sees it

The task closes on the Operations Board with the note and photo attached. Nobody chased anyone, and nobody asked "did that get done?"

Paint the trim in the youth room
Jordan P. · done Sat 10:14am · 1 photo
Our Serve Board: a public list of jobs around the church, each with an I'll do this one button.

Our Serve Board

Work anybody in the congregation can pick up.

A public page of jobs around the church. People put their name to one, tick it off when it's done and can subscribe to a weekly email of what's still open. No account, ever.

"No account, no password. Put your name to something and we will take it from there."

The office side

One place the whole office runs the week from.

Staff sign in and work here. Events, trips, projects, tasks, the building, the calendar and the conversations sit together, so nobody keeps five tabs open to answer "who, when, where."

worksite · Ops Board
The Ops Board: an urgent notice, nine green job lights, counts of overdue and upcoming work, the clock and the calendar strip.

Ops Board

The hub. Every project and task, what is overdue and what is waiting on you. An urgent notice reaches the whole staff; nine small lights turn red only when a scheduled job stops; the strip along the top is the next few days from Planning Center.

Every Site

Everything a church office juggles, in one place.

Green marks the pages people use without an account. Every tile opens its screen above or below.

The rest of the building

The parts nobody sells you, because nobody else runs a building.

The serving roles, the broken heater, the electrician's insurance, the safeguarding policy, the guest from Sunday. Each has a page, and each page knows about the others.

worksite · Team One
Team One: eleven roles across departments, fourteen people in post, and the two roles still needed.

Team One

A written description for every serving role: what it is, what you will do, what helps, the time it takes and why it matters. Who holds each one, who used to, and the open roles posted on ServeSite so a person can ask about one without an account.

No account, no password, no app

Eleven pages that work from one link in a text.

Each one shows a person their one thing and nothing else. The link is theirs; it cannot reach anybody else's job, form or quote. This is what the volunteers, parents, vendors and guests see, on the phone in their hand.

One job on a phone: Paint the trim, a note box, a photo button, Mark it done.
One jobFrom a TaskSite, EventSite or ProjectSite. A note, a photo, a button.
ServeSite on a phone: jobs around the church, each with an I'll do this one button.
ServeSiteWork anybody in the congregation can pick up. Put your name to it.
A maintenance request form on a phone: where, what needs fixing, a photo, how urgent.
Report a problemA leak, a flicker, a loose rail. It reaches the office with the photo.
A meeting invitation on a phone: when, who, and yes, another time, or can't make it.
A meetingYes, another time, or can't make it, from the email. Add it to your calendar.
A vendor's page on a phone: what you're doing, the dates, and the drawings shared with them.
A vendor's scopeTheir part of the project, the dates, the drawings. Nobody else's quote.
A staff member's desk on a phone: counts, the clock, the week's calendar.
And for staff, the whole thingAdd it to the home screen and it opens like an app, with phone alerts.

The other five: a parent's consent form, a trip sign-up, a Team One enquiry, a guest's coffee invitation, and the reply to any Worksite email, which lands back in the conversation it came from.

A week at Riverbend

What happens without anybody pressing anything.

Nine scheduled jobs run the week. Every one of them reports when it stops, so the office finds out the same day rather than in March.

  1. Sunday, 11:52amA first-time family fills in a connect card. Within fifteen minutes they have a welcome text; that afternoon, a follow-up. At 2pm leadership gets the list of guests nobody has spoken to yet.
  2. Monday, 7:00amEvery administrator gets the weekly digest: the whole operation on one screen, whether or not the news is interesting.
  3. Every morning, 7:30amThe roundup. Each person gets one email of what landed on their desk since yesterday. Anyone with nothing new hears nothing.
  4. Weekdays, 1:00pmThe nudges. Anyone with something overdue, something due within three days, or a desk they have not opened in a week.
  5. Every hourPlanning Center's calendar and people are pulled down, so the board is never a week behind.
  6. Every minuteReplies to Worksite emails are read out of the mailbox and put into their conversations.
  7. Friday, 9:00amThe ServeSite digest: everyone who put their name to something hears what is still open. In a week when nothing is, it sends nothing.
  8. Every night, 2:30amThe backup, kept for two weeks, with a second copy to the church's own OneDrive. Any update we have published installs straight after it.
  9. Once a day, only when it is true"A scheduled job has stopped." One email to the administrator, from whichever job is still running.

Questions we get on every walkthrough

The straight answers.

Do our volunteers need to make accounts?

No. That is the whole design. A volunteer gets a text or an email with one link to one page. They can finish a job, claim a Saturday, sign a form or answer a meeting without ever seeing a sign-in screen. Only staff sign in, and even they can keep a device signed in for two weeks or use Face ID.

Do we have to use Planning Center?

Worksite is built beside it, not instead of it. People, the calendar, service plans and connect cards come from Planning Center and stay there; Worksite never becomes a second copy you have to maintain. If you are not on Planning Center, the Sites, TaskSite, ServeSite, Team One and messages all still work; the calendar and guest pages would sit empty until you are.

What do we need to have already?

Planning Center, Microsoft 365 for email, and Clearstream for texting. They stay on your own subscriptions. We connect all three during the setup month, using your own credentials, and each one is optional in the sense that if it is not there, that feature switches off rather than breaking.

How long does setup take, and what do we have to do?

The first month. We build your Worksite, connect the three services (a Microsoft 365 administrator clicks one consent screen), import your people and roles from a spreadsheet, set your gathering days, put your logo on it, and hand it over on a short call. Your part is about an hour: the spreadsheet, the consent click, and telling us who is who.

Where is our data, and can we get it out?

On a server we rent in the United States, in a folder and database that belong to your church alone. Your owner can download a complete copy any time from the Backups page, and a second copy can go into a person's OneDrive in your own Microsoft 365. When you leave, you take it with you and we delete ours. The privacy page says exactly what is stored and what ever leaves.

What do the texts cost?

Texts go out through your own Clearstream account on its credits, so the cost is whatever Clearstream charges you; Worksite adds nothing. Before any group text goes, you see the recipient count and the credit cost, and texting the whole church takes two screens and a fifteen-minute pause on purpose.

Is there an app?

Worksite is a web app that installs to a phone's home screen in two taps and then opens like an app, with phone alerts if you want them. There is nothing to find in an app store and nothing for a volunteer to install at all; their link opens in whatever they already have.

Who can see what?

Staff see their desk and the Sites they are on; administrators see the whole church; the owner alone can download the backup. A conversation is private to the people in it with no administrator override. Trip consent and medical forms are encrypted with a key that lives outside the database, and only that trip's leaders can open them. A one-link page reaches one job, one form or one quote and nothing else.

What happens when something breaks?

Worksite watches itself. If a scheduled job stops, if email is being refused, or if the backup is old, the administrator gets one email that day, and so do we. Updates install overnight after the backup and keep the previous build, so anything that goes wrong can be put back. If you ever cannot reach us, nothing pauses: the last answer stands for two weeks.

Can our church put its own name and logo on it?

Yes. Your name, colours, logo and icons are yours from day one, on every page, in every email and on the home-screen app. "Team One" is whatever you call your serving teams.

We have two campuses.

Worksite Plus is sized for a larger staff and more than one campus, with every Site able to carry a campus. On a walkthrough we will show you how another church runs it that way.

What does it not do?

Check-in, giving, worship planning and background checks. Those belong to Planning Center and we never touch them. Worksite covers the work around the database: the events, the building, the jobs, the vendors, the volunteers and the conversations, which is the part nobody else sells you.

What if we cancel?

No contract. Cancel from the billing page and your Worksite runs to the end of the month you paid for, then becomes read-only for two weeks so you can export everything, then we delete it. The setup fee is not refunded once the setup work has begun.

Built by someone who has run a church

The details you only think of after a few Sundays.

A text is not a welcome.

A first-time guest gets a text within fifteen minutes and a follow-up a few hours later. Leadership's report lists guests by who hasn't been spoken to by a real person yet, because a text buys an hour. It doesn't do the welcoming.

The debrief that pays for itself.

After an event, six questions. Each line under "what to change next time" becomes a task on next year's plan. What took years to learn stops living in one person's memory.

The biggest button is the hardest to press.

Texting the whole congregation takes two screens and typing the list's name by hand. You see the recipient count and the credit cost before you commit, and then there's a fifteen-minute pause. Nothing ever sends it automatically.

Nobody is texted twice.

A church that texts a first-time guest twice in an hour has introduced itself badly. Worksite marks the welcome as sent before it goes, so a slow network never causes a double send.

Private means private.

A conversation is private to the people in it, with no administrator override. Consent and medical records are encrypted and can be deleted after the trip.

It tells you when it's broken.

Eight scheduled jobs run the reminders, digests and syncs. A warning light appears only when one of them hasn't run, because an "all systems normal" panel stops being read after a week.

Who built it

Built by someone who has done every job in the building.

Worksite wasn't built by a software company that studied churches. It was built by someone who has served in the church for many years, and who has done most of the jobs Worksite now organizes.

He's cleaned the rooms and set out the chairs. He's led the creative department and now runs operations as the church's chief operating officer. Every screen in Worksite answers a question he was asked on a Sunday morning, or one he had to chase down on a Tuesday.

Craig Gwin Founder, CityTree Development

  1. CleaningLearned the building from the floor up.
  2. SetupSet out the rooms, the chairs and the stage, week after week.
  3. Creative leadLed the creative department through every event, series and Sunday.
  4. Chief operating officerNow runs operations: the building, the calendar, the staff and the events.

Keep what you already pay for

It sits beside Planning Center. It doesn't replace it.

Nobody wants to move their church database. Worksite reads what your other tools already know and puts it where people will see it.

Your subscriptions

  • Planning CenterPeople, Calendar, Services, Forms
  • Microsoft 365Sends and receives the email
  • ClearstreamSends the texts on your credits
WORKSITE

Brings them together. The office works here, and the people doing the work get what they need.

Where people already are

  • Their inboxReminders, digests, requests and replies
  • Their phoneA text with one link to one job
  • Their calendarA subscription that stays up to date

We connect all of it for you during setup. Each connection is optional. If one is off, that feature switches off rather than breaking. Worksite deliberately never touches Giving or background checks.

Who it's for

The person holding it all together.

An executive pastor, COO, business administrator or operations director. You run the building, the calendar, the events and the staff with a spreadsheet, a group text and your own memory. It fits churches of roughly 150 to 2,000 on a Sunday, with a handful of staff and a lot of volunteers.

What it isn't

Not another church database.

Worksite doesn't do check-in, giving or worship planning. It covers the work around the database, the part no one else sells you. Its real competitor is the spreadsheet, the group text and the room everybody assumed somebody else had booked.

11pages people can use without an account
9scheduled jobs that report when they stop
77test suites, all passing
0servers for your church to run or install

Pricing

One flat price. We set it up in month one.

A one-time setup of $250 covers the first month: we build your Worksite, connect Planning Center, Microsoft 365 and Clearstream, load your people and roles, and hand it over ready to use. The monthly plan starts in month two. Hosting, backups and every update are included. No contract; cancel any time.

Worksite

$129/month

For churches up to about 750 on a Sunday. $250 setup, then $129 a month from month two.

  • Every Site: events, trips, projects, tasks, maintenance, vendors
  • Our Serve Board and Team One roles
  • Email and text reminders, digests and one-link jobs
  • Planning Center, Microsoft 365 and Clearstream connected for you
  • Unlimited staff and volunteers
  • Setup, hosting, backups and updates included
Start your setup month

Worksite Plus

$199/month

For churches over about 750 on a Sunday, or with more than one campus. $250 setup, then $199 a month from month two.

  • Everything in Worksite
  • Sized for a larger staff and more ministries
  • Guest welcome texts and leadership reports
  • A yearly review of how your church is using it
Start your setup month

What the setup month looks like

  1. Week 1You sign up; Square takes the setup fee. We build your Worksite at its own address and send you the spreadsheet for people and roles.
  2. Week 2We connect Planning Center, Microsoft 365 and Clearstream with your credentials, and load your people, roles, departments and gathering days.
  3. Week 3Your logo, colours and words go on. We set the scheduled jobs running and watch them for a few days.
  4. Week 4A short call to hand it over. Your staff sign in; the first monthly payment is on day 31, and we remind you a week before.

Worksite works alongside the services your church already uses. Planning Center, Microsoft 365 (email, calendar and Teams) and Clearstream for texting are each connected during setup and stay on the church's own subscriptions. Payments are handled by Square; we never see your card number. The setup fee is charged when you sign up, the first monthly payment is 30 days later, and we'll remind you a week before. Not sure which plan fits? Ask for a walkthrough.

Get started

We set it up. You sign in.

There's nothing for your church to install and no server to look after. We handle the whole setup personally, so your staff can start using Worksite instead of configuring it.

  • SetupYour staff, rooms, Sites and Team One roles, ready on day one.
  • IntegrationWe connect Planning Center, your email and your texting service.
  • HostingWorksite runs on our servers. We keep it running and up to date.

Tell us a little about your church and we'll set up a walkthrough — a live look at Worksite running for Riverbend, an invented church, with your questions answered as we go.

We'll only use this to write back to you.