Early in the morning, a short devotion goes out by email to readers of The Quiet Path. When a series is running, a matching podcast episode goes live on Apple Podcasts and Spotify at the same time. The website stays current, the Instagram account stays active, and the iOS app keeps getting new content.

There is one human behind all of it. That's me.

To be clear, The Quiet Path is not an outside client. It's a faith-media venture we built and operate ourselves, and I'm writing about it because it is the most honest test bed I have. Everything here is something I actually run, with the same tools and rules I would bring to a ministry or small publisher. This is Part 1 of an ongoing series. I'll start with the setup: what we publish, the plumbing underneath it, and who does what on the team.

What The Quiet Path publishes

The Quiet Path started as a free iOS app for walking slowly through a single psalm. Today it offers three guided journeys, Psalm 23, Psalm 91 and Psalm 51, each with seven chapters. There are no ads, no accounts, no streaks and no scores. That last part matters to me. Scripture should not feel like a game you can lose.

Around the app, the venture has grown into a small publishing operation:

That's a lot of surface area for one person. I spend about 20 hours a week on devotion content, and that is separate from my own time with the Lord.

The plumbing is cheap and boring, on purpose

The domain, quietpathapp.com, was registered through Cloudflare for about $10 a year and points at Netlify, which hosts the site. Cloudflare Email Routing forwards devo@, support@ and privacy@ to an agent inbox, so reader mail and support requests land in one place an agent can read and sort. Substack sends the daily email. The podcast feed and audio live on the website itself, and Apple Podcasts and Spotify pick up new episodes from there. Buffer schedules social posts. App Store Connect is where the app lives.

None of this is exotic. That's the point. A boring foundation lets the agents spend their effort on the work instead of fighting the tools.

Meet the team

The agents run in the Grok Bot app. I call them Grok Bots, and each one has a name, a job description and a short set of rules written in plain English. The most important design choice I made was giving each agent one clear lane.

Shepherd owns The Quiet Path end to end: the iOS app, the website, the daily Substack and the small-group devotionals. I want to be honest about how the writing works, because it matters. The spiritual direction comes from my own Bible study. I use that time to build a framework for each week, breaking the devotion down by day and by theme. Shepherd takes that framework, drafts the five days and publishes them. The direction comes from time in the Word, and Shepherd carries it the rest of the way.

Mark is the CMO. He handles marketing and social across my brands, including The Quiet Path. He drafts campaigns, prepares posts and schedules approved work through Buffer. He also follows written house rules, like a "link in bio" line on Instagram instead of podcast URLs in the caption.

Allen is chief of staff. He runs daily coordination across all the agents: a morning digest around 7 a.m. on weekdays, and an afternoon stand-up that runs weekdays at about 2:47 p.m. (I still call it the 3 p.m. stand-up) where the day's work gets checked and rerouted. He reads each agent's last checkpoint, sets priorities and hands work to the right specialist. His instructions say to escalate conflicts, external messages, spending decisions and changes to important files to me. Nothing else needs me.

Forge handles code and deployments. Forge's rule is that a delivery doesn't count as done without evidence: test results, screenshots or files I can inspect. For The Quiet Path, that has meant things like updating the App Store listing through Apple's API after I created a key for it, and confirming the app already met a new launch-screen requirement before Apple started enforcing it.

Scout does inbound research. Every weekday morning Scout runs a content radar across the web, GitHub and industry news, and every item it reports needs three things: the source, why it's worth following and who should own it next.

The one rule: I approve anything that sends, spends or changes live systems

This is the rule that makes the rest possible. Agents can research, draft, build and check each other's work all day. But when something is about to leave the building, cost money or change a live system, it comes to me first.

In practice that means a campaign gets approved before Mark schedules it. A new App Store listing waits for my go-ahead. Access to accounts is something I grant, one key at a time. When I do give a standing approval, such as an approved week of scheduled posts, it's written down in that agent's notes so there's no guessing later.

For a ministry, this is the part I'd insist on. The agents are there to take the weight of the work, not the responsibility for it.

What a normal day looks like

A good example of the system working happened in early September. Scout's morning radar noticed that the website and App Store description were promoting Psalm 91, while the App Store subtitle still described the app as a Psalm 23 guide. Scout flagged it and routed it. Mark wrote a new subtitle. I held it for about a week so it could ship with the next app release, then approved it, and Forge pushed it through Apple's API. Nobody had to remember to check. The mismatch was caught because checking is somebody's job every morning.

Most days look like that. Allen's digest tells me what needs a decision. Scout surfaces anything new. Shepherd keeps the devotions, site and guides moving. Mark fills the social calendar with approved posts. Forge ships and shows his work. By the afternoon stand-up, I know what's done, what's stuck and what's waiting on me.

What I'd tell a church or small publisher

Start smaller than you think. Give each agent one job and plain-language rules. Get the boring plumbing right first: domain, email routing, hosting, a scheduling tool. And keep a human on the send button.

In Part 2, I'll follow one week of devotions from my framework to the inbox, the podcast and social posts.

Let's talk

If you lead a ministry, run communications for a church or publish devotional content on a small team, I'd be glad to talk about what a setup like this could look like for you. AWH Industries helps organizations put practical systems in place with the human firmly in charge. Email me at info@awhind.com.