Case study · Operations tool · Ottawa

One place for the budget and the money.

Lighthouse Church Ottawa runs four campuses. Its budget lived in a workbook, its spending in QuickBooks and its events in Planning Center. I built Lighthouse Admin so team leads, pastors and finance could all work from the same numbers.

Budget overview · FY 2027Example data
Requested
$248,600
118 lines
Approved
$172,400
of $196,700 reviewed
Awaiting review
$51,900
34 lines
Event-related
$96,200
9 events

Requested and approved, by month

By campus

  • Downtown$84,200
  • North$71,500
  • East$56,300
  • West$36,600
campuses on one system
4
roles, enforced in the database
5
outside systems connected: QuickBooks and Planning Center
2
automated tests run on every push
184

The problem

Three systems. No shared answer.

Who asked for what? What got approved? Are we on budget? Each answer meant lining up separate tools by hand.

  • The plan

    A workbook

    The 2026 budget lived in a spreadsheet, with its campuses, teams, cost centers and events kept on a tab of drop-down lists.

  • The money

    QuickBooks

    Actual spending was recorded in the books, with nothing tying a transaction back to the plan.

  • The calendar

    Planning Center

    Event dates were kept here, away from what those events were budgeted to cost.

  • The people

    Four campuses

    Team leads needed their own campus, leaders needed all of them, and finance needed the books.

The thinking

Six decisions that shaped it.

Money and access were the risks, so those decisions came first. Features could change later. Trust in the numbers couldn’t.

  • 01

    Start with one job

    Version one did only the budget: submit, review, report. New areas became sections on the same foundation, so it could grow without a rewrite.

  • 02

    Put the rules in the database

    Who can see and change what is enforced in Postgres, not just on screen. Going around the app gets the same answer as using it.

  • 03

    Design for the team lead’s phone

    One link to paste in a team chat, a sticky Add button and tappable cards. Asking for a budget line shouldn’t need a laptop.

  • 04

    Leave the source of truth alone

    QuickBooks stays the books and Planning Center stays the calendar. The app reads from them and never posts to the books.

  • 05

    Be honest about gaps

    Spending that can’t be matched shows as not matched. A sync that finds nothing explains why, instead of saying all is well.

  • 06

    Make it safe to try

    Test mode switches one admin’s browser to a full copy of the data. It sends no invites and can’t touch QuickBooks.

The solution

From request to actual spend. One line of money, followed the whole way.

01

Asked for. Decided.

Team leads add a line once and pick its months. Reviewers approve it in full, approve part of it or decline it, one at a time or in bulk.

  • Only your campus.Leads see and add lines for their own campuses, while the year is open.
  • Every review stamped.Who decided, when, and for how much is kept with the line.
ApprovalsExample data
  • Stage lighting rentalProduction · Downtown · Mar$3,400
  • Volunteer appreciation dinnerHospitality · North · Jun$2,200Approved
  • Speaker travelEvents · East · Sep$4,100$2,800 approvedPartly approved
  • Kids check-in labelsKids · West · Sep$650
02

Tracked against the books.

Budget watch matches QuickBooks accounts and classes to cost centers and campuses, then shows the plan against what was actually spent.

  • Plain-language findings.What stands out is written in a sentence, not left in a chart.
  • Last year as a reference.FY 2027 is planned against real FY 2026 spending.
Budget watch · Who’s on trackExample data
  • Downtown$58,900 of $64,00092%On track
  • North$45,900 of $41,000112%Over
  • East$36,200 of $38,50094%On track
  • West$25,100 of $27,00093%On track

North has spent 12% more than its budget to date.

03

Tied to the calendar.

Events sync from Planning Center, and budget lines attach to them, so an event’s dates and its cost finally sit in the same place.

  • Edits here stick.A change in the app survives the next sync. Deleted imports can be restored.
  • Right campus, automatically.Events land on the campus named in their location or tags.
Events · The year at a glanceExample data
04

Flags what’s missing.

The hardest gaps to spot are the things that never happened. The system looks for them, and every change lands in an activity log.

  • Finds the silence.A campus with no lines, or a team that budgeted last year but not this year.
  • Tells the right person.Declines arrive with the note, and approvals are merged into one message.
Needs attentionExample data
  • West has no budget lines yetCampus with nothing submitted this yearCampus
  • 2 teams budgeted last year, but not this yearParking and Prayer at NorthTeams
  • Submissions close in 6 daysDeadline for FY 2027Deadline
  • 11 reviews waiting over a weekOldest request is 12 days oldReviews

The improvements

What changed, and why.

75 commits in about a day, each small enough to use and rethink. The first version of an idea was often not the one that stayed.

  • Events

    BeforeTwelve month cards.

    NowA year timeline with one lane per campus, after trying a month strip and a heatmap.

    WhyBusy and empty stretches, and which campus they belong to, show without any reading.

  • Approvals

    BeforeCollapsible groups by campus.

    NowOne flat list with campus filter chips and counts.

    WhyReviewers can compare across campuses and see what’s waiting without opening anything.

  • Joining

    BeforeA separate join link for each campus.

    NowOne team link. People choose their campus when they join.

    WhyOne link to share and manage. Admins are told who joined which campus.

  • Access

    BeforeAdmin or team lead.

    NowFive roles, including campus pastor, finance and manager.

    WhyFinance can work the books without approval rights. Managers get people and the activity log.

  • Spending

    BeforeBudget watch for admins only.

    NowTeam leads see their own campus, from monthly totals.

    WhyLeads can stay on budget without seeing payees, memos or transactions.

  • Calendar sync

    BeforeOnly weekly repeats left out of the import.

    NowAny series that repeats three or more times a year is left out.

    WhyRehearsals and leads meetings stop crowding out the events that carry a budget.

Tested against reality

What broke, and what it taught me.

Sample data is polite. Real ledgers and real sign-ins aren’t. Each fix added a clearer message or a test, so the same failure can’t return quietly.

  • Real data

    5,299 rows, no amounts

    The church’s QuickBooks company silently dropped the amount column I asked for, so nothing was kept. Now the sync reads whichever amount form comes back, falls back to the standard ledger, and explains an empty result.

  • Real flows

    A sign-in rule in the way

    A sign-in fallback caught the code QuickBooks sends back when you connect, and bounced admins to the login page. I excluded API routes, added a test for it and logged every failed connection with its reason.

  • Real load

    A soak test for every role

    Each main screen is rendered for each role with empty data, realistic data, 3,500 lines and hostile input: huge amounts, bad dates and junk URLs. The test fails if anything crashes.

Where it stands

Live, and still growing.

Lighthouse Admin is live, with FY 2027 being planned against real FY 2026 spending.

It began as a budget tool. It now covers budget, finance reports, events and people, and each new section reuses the same roles, activity log and data.

  • Next.js
  • Postgres with row-level security
  • Supabase Auth
  • Vercel
  • QuickBooks Online API
  • Planning Center calendar feed
  • Vitest
  • GitHub Actions

FAQ

Questions.

Does this replace QuickBooks or Planning Center?

No. They stay the source of truth. Lighthouse Admin reads spending from QuickBooks and events from Planning Center, then adds what they don’t do: budget requests, approvals, and a view of the plan against the actuals.

Could you build something like this for a business?

Yes. Requests, approvals, roles and budget against actuals apply to any organization with several teams or locations. I’d start from how your team works today, and connect the accounting and scheduling tools you already use.

Is any church data shown on this page?

No. Every screen here is rebuilt with invented campuses and figures. Real budget and giving data stays inside the app, behind sign-in.

Taking new projects

Tell me what’s slowing you down.

I reply personally within one business day, with a time for a free 30-minute call.

Or emailcontact@dinebari.comOttawa, Ontario. Working across Canada and the US.