Why we're called Trellistry

A trellis is not the point. But nothing grows well without one.

The idea we borrowed

In 2009, Colin Marshall and Tony Payne published a short book called The Trellis and the Vine. Its picture is simple.

The vine is people — the slow, personal, prayerful work of helping someone come to faith, grow toward maturity, and go on to help others do the same.

The trellis is everything built to hold that up. Buildings, budgets, rosters, committees, programmes, policies, paperwork.

Both are needed. But the trellis has a habit of taking over. Trellis work is visible, urgent and easy to measure, so it quietly expands until a week that was meant for people has been spent maintaining a structure instead. An organisation can look busy and well-run while the thing it exists for is being squeezed.

Where we come in

For all its influence, the book says far more about the danger of the trellis than about how to build a good one. That gap is our work.

Trellistry is trellis plus ministry — and plus the old sense of a craft practised carefully. We build the supporting structure so you can get back to the vine.

We are not trying to do vine work for you. Software cannot disciple anyone, counsel anyone, or teach anyone. What it can do is take the roster, the reschedule, the reminder and the sign-up form off your desk — and then help you think about what to do with the time you get back.

We build for organisations whose people spend their week coordinating instead of caring — and that problem looks the same in a church, a family service centre and a school. A trellis is the structure that holds up living growth: necessary, but it should never become the thing you spend your week maintaining.

What the name commits us to

• We measure ourselves by hours handed back to you, not by how long you stay in our product.
• We'd rather train someone than fill a gap. One of the book's own mind-shifts is moving from plugging vacancies to growing workers — which is why our training runs as a service in its own right, and not only as software onboarding.
• Your case notes, chats and pastoral records are vine work. They stay on our own infrastructure and never go to public AI services.
• We might tell you not to buy our software. A design workshop may conclude you don't need it — and we'll invoice for the workshop and walk away.

The trellis behind thriving ministry.

That's the tagline. It is a statement of purpose. The work we do is structure — rosters, records, coordination, follow-through — and the reason to do it well is so the real work, the vine work, can grow.