Complex website and content platforms
Start at $15K+
Typically implemented with Next.js and Payload CMS when the project includes content architecture, migration, integrations, and governance complexity.
How I Work
One senior path from business problem to production system.
I work directly across business discovery, architecture, hands-on implementation, clearly bounded team workstreams, migration, launch, and stabilization.
Ownership and limits
I work with a maximum of three active clients at any given time. This cap is intentional and non-negotiable so I can concentrate senior attention on business context, architecture, high-consequence technical decisions, critical implementation, migration, and rollout—where judgment has the greatest impact.
Visual and interaction design is handled by Katharina, a partner I've worked with for three years. I remain accountable for the technical direction, system architecture, integration model, and coherence of the system through delivery.
I came into development from marketing and sales, then learned full-stack systems before modern AI coding tools became capable. That means AI now accelerates implementation on top of hard-won system judgment, not instead of it.
Delivery
Engagement phases
01
Discovery and ecosystem mapping
Map websites, content, teams, workflows, permissions, integrations, data flows, migration risk, and stakeholder requirements before implementation scope is locked.
02
Architecture and shared decisions
Define the target platform, content model, decision rights, system ownership, integration boundaries, shared technical contracts, infrastructure, and rollout sequence. Establish where teams can work independently without creating competing systems.
03
Implementation or team enablement
Build the critical application, CMS, data, infrastructure, and integration foundation directly; structure clearly bounded work for internal or external teams; or combine hands-on delivery with senior technical review. Shared architecture and integration decisions remain explicit while teams execute independently.
04
Migration, launch, and stabilization
Execute migration, redirects, integrations, launch checks, training, and post-launch stabilization so the platform becomes owned by the organization.
Modes
Engagement modes
Full discovery and implementation
I define the platform foundation and then lead the build through UX collaboration, CMS, frontend, application logic, infrastructure, migration, integrations, launch, and stabilization.
Architecture followed by team implementation
I deliver the blueprint and remain involved at defined technical decision points while your internal team or delivery partner executes clearly bounded workstreams.
Focused technical advisory
For teams already building with Next.js and Payload CMS who need high-risk decisions, architecture review, or implementation oversight.
After the first engagement
The next step depends on system maturity and business needs, not a preset retainer model.
- A second build phase to extend the system
- Incremental iteration and expansion as the business evolves
- Transition into a lighter advisory or system-oversight role
Advisory for in-house teams
If your team is already implementing with Next.js and Payload CMS, I also offer a technical advisory path: architecture direction, tradeoff guidance, integration-boundary definition, and risk review while your team executes.
This is advisory, not staff augmentation. See advisory details.
Communication
The goal is clarity and momentum, not meetings for their own sake.
- Day-to-day communication happens asynchronously through Slack, chat, email, or Teams.
- For major decisions, system inflection points, or alignment moments, we use scheduled calls.
- Decision and progress checkpoints are agreed around the points that affect the shared system, with continuous access to the working environment where applicable.
Investment
Pricing entry points
Focused implementation
Start at $5K+
A bounded implementation path for a specific workflow, integration, AI, or internal-tool problem after the foundation is clear.
Final pricing depends on scope, complexity, and system depth defined during the initial phase.
Fit
Scope
This is for you if
- You are an established organization dealing with fragmented sites, content systems, workflows, or migration decisions.
- You want direct senior ownership connecting business, UX, data, application, infrastructure, and content decisions.
- You care about maintainability, ownership, and rollout risk over quick feature delivery.
- You value direct access, clear thinking, and end-to-end ownership.
Not a fit if
- You are looking for an agency with parallel workstreams and larger delivery teams.
- You need ticket-based execution, staff augmentation, or task outsourcing.
- You want AI features without addressing underlying system issues.
- You are optimizing for lowest initial price over long-term impact.
How to start
Start with a short conversation to walk through your business context, current setup, and platform goals.
Fit Call
Discovery Call
Free · 25 minutes
A short call to see if there is a fit. You tell me what is not working with your website, content system, workflow, or digital infrastructure. I ask a few direct questions. We both decide whether it makes sense to go deeper. No pitch, no presentation.
Book a discovery callNeed architecture clarity before a conversation?
If you need an independent evaluation of your CMS proposal, platform architecture, or ground-up blueprint before starting a build, the CMS Architecture Review & Platform Blueprint provides three fixed-scope engagement tiers to resolve architecture decisions before coding.