ReedVerde brandmarkReedVerde
    Back to Blog

    What a Discovery Session Actually Looks Like

    Reed VerdesotoReed VerdesotoDigital Systems Architect
    What a Discovery Session Actually Looks Like, custom Subsplash blog by ReedVerde

    Most churches that contact me want a website. What they actually need is architecture.

    There is a difference. A website is a collection of pages. Architecture is the system that determines what those pages are, how they connect, who they serve, and how they stay current after launch. Without architecture, every website eventually drifts into the same mess that prompted the redesign in the first place.

    That is why every ReedVerde engagement starts with Discovery. Not a sales call. Not a scope meeting. A structured architectural process that maps your entire digital ecosystem before a single page gets built.

    What Discovery Is

    Discovery is a $1,500 one-time investment. It is the planning phase before any build, migration, or redesign begins.

    If you were building a home, you would not hire the builder first. You would hire the architect. You would design the structure, determine how people move through it, define where systems connect, and decide what must be protected from constant change before anyone pours concrete.

    That is what Discovery is. I step in as your strategic digital architect. Together, we design the space you are going to operate inside before we build it.

    How the Process Works

    We meet in focused one-hour sessions, typically one to two per week. You only need to book the first session to begin. From there, I guide the process based on what your organization actually needs.

    In these sessions, we map your strategic goals and what digital infrastructure needs to support them. We define your audiences and how each one should experience your digital presence differently. We document your content architecture, including what pages should exist, how they connect, and what hierarchy governs them. We trace your workflows and communication flow so that nothing gets duplicated or lost. We identify platform constraints, integrations, and where tools overlap or conflict. We clarify governance and decision authority so the system survives staff transitions. And we account for your operational realities and team capacity so the plan is executable, not aspirational.

    What You Receive

    Discovery produces a documented system map with priorities, a recommended scope for the build phase, phases of execution broken into clear sprints, a build plan tied to your actual resources, and final project pricing for the build.

    You walk away knowing exactly what needs to be built, in what order, at what cost, and why. There is no ambiguity. There is no "we will figure it out as we go." Every decision is documented before execution begins.

    Why This Prevents the Rebuild Cycle

    Most churches rebuild their website every two to four years. They pay $5,000 to $15,000 each time. The new site looks great at launch and slowly drifts into the same disorganized state as the old one. Pages get added without strategy. Navigation grows until nobody can find anything. Content duplicates across the site and the app. Staff changes and nobody knows how the system works anymore.

    This cycle exists because those rebuilds skipped architecture. They went straight to design and development without asking the structural questions first. The result looks different but functions the same way.

    Discovery breaks the cycle by building the system before the site. When architecture leads, the website is a reflection of decisions that were already made. Content has a home. Navigation has logic. Governance has documentation. And when something needs to change, the team knows how to change it without breaking everything else.

    What Discovery Is Not

    Discovery is not a commitment to build with ReedVerde. If we go through Discovery and determine that your needs are better served by another provider, a different platform, or an internal team, you still have the architectural document. It is yours. It works with any builder.

    Discovery is also not a design phase. We do not produce mockups, wireframes, or visual concepts. We produce the structural blueprint that design and development will follow. Design without architecture is decoration. Architecture without design is a plan waiting for execution.

    Who Discovery Is For

    Discovery is for churches and organizations that are tired of rebuilding. It is for teams that have outgrown their current setup and know that the next phase needs to be different. It is for leaders who want to understand their digital ecosystem, not just hand it off to a vendor and hope for the best.

    If your website is more than two years old and you are already thinking about a redesign, that is the signal. The redesign impulse is your system telling you that architecture was missing from the beginning.

    Start with Discovery. Build the plan. Then decide how to execute it.

    Originally published on reedverde.com