This page is not a list of random favorites. It is a view into how we think about platforms, components, workflows, and information sources across Web, AI, DO/IT, Marketing, Product Management, and Coaching.
Where we do name products, treat them as current preferences rather than eternal dogma. Good recommendations are situational. Good judgment beats brand loyalty.
We apply the same practical filters to every meaningful recommendation:
Is it maintainable by a serious provider over time?
Does it support portability, or does it create avoidable lock-in?
Does it meet or exceed applicable standards?
Does it have credible support, documentation, and update behavior?
Does it fit the project’s real budget, staffing, and change cadence?
Can it be supported cleanly at implementation time and during ongoing care?
We also distinguish carefully between what becomes part of the implementation itself and what depends upon ongoing provider-side care. Implementation-side choices should remain useful and supportable even if a project later moves to another provider. Care-side capabilities are different. Some are dependent upon our own environments, processes, and operational controls, and therefore do not travel automatically with the implementation.
Our recommendations are designed to support both lean Core builds and more expansive Supercharger-style growth when the project warrants it.
Different platforms are good at different jobs. We do not treat them as interchangeable.
Web
WordPress, Astro.js, Webflow, and HubSpot each solve different classes of web problems. The right choice depends on feature profile, editorial needs, design requirements, governance needs, performance targets, and expected growth.
AI
Reasoning, retrieval, research, workflow orchestration, and media generation do not all demand the same tool. We recommend AI stacks by task, by control model, and by risk profile.
DO/IT
Release operations, access control, DNS, backup and recovery, observability, and continuity planning are not glamorous, but they decide whether a project is stable or fragile. Many projects in other Areas of Interest depend upon DO/IT choices, even when DO/IT is not the headline.
Marketing
Recommendations in marketing must support clear messaging, measurable outcomes, channel fit, and manageable operating burden. A flashy stack that no one can run properly is not a smart recommendation.
Product Management
Tool choices should support goals, requirements, prioritization, visibility, and progress review. They should not create more ceremony than value.
Coaching
Recommendations in coaching and education should reduce confusion, improve capability, and support continuity. The best tools here are often the ones that help people actually adopt the work rather than merely admire the theory.
We build web projects primarily on a small number of platforms because depth is more valuable than stack tourism.
WordPress is often the right answer when a project needs deep extensibility, strong editorial flexibility, broad feature options, and room to grow beyond its first brief.
Astro.js is often the right answer when performance, component discipline, static or hybrid delivery, and tighter front-end control are central to the project.
Webflow is often the right answer for design-led marketing sites with controlled complexity, visual management needs, and tighter authoring boundaries.
HubSpot becomes more attractive when the website is tightly bound to CRM, lifecycle automation, lead flow, and broader marketing operations.
We do not choose among these by ideology. We choose by fit. That includes the feature set, the team’s operating reality, the likely change rate, the care burden, and the cost of getting boxed into the wrong choice.
We recommend AI tools by job, not by hype cycle.
For reasoning, drafting, and assistant-style work, we favor mature ecosystems that deliver practical value and can be governed sensibly. For research acceleration, we favor tools that surface useful material rapidly without pretending that validation has become optional. For image, sound, and video work, we prefer platforms that allow meaningful art direction instead of slot-machine randomness. For agentic and workflow-oriented work, we care most about grounding, controls, routing, reviewability, and maintainability.
Our preferred stack commonly includes platforms such as ChatGPT and Claude for high-value language work, Perplexity for research acceleration, and the Stable Diffusion and Midjourney ecosystems for image development, depending on the creative and operational requirements. We also evaluate additional model and checkpoint options where private rigging, specialized behavior, or R&D work makes that worthwhile.
AI recommendations should support more than novelty. They should support quality baselines, prompt frameworks, safeguards, reporting, and realistic long-term operation.
Recommendations are not only about websites and AI interfaces. They are also about the systems that keep those projects healthy.
We commonly recommend operational layers that improve security, release discipline, visibility, and continuity. That includes infrastructure and edge services, deployment pipelines, access control patterns, observability, backup and recovery posture, and the practical glue that keeps digital systems from drifting into expensive folklore.
Cloudflare plays an especially important role in much of our work because it can strengthen security, delivery, DNS control, caching strategy, redirects, and edge behavior without forcing every project into the same narrow box.
On the growth side, we recommend tools based on operational fit. Some teams need a CRM-centered marketing machine. Others need a leaner and cleaner composition of simpler tools with clearer ownership boundaries. The right answer depends on team maturity, reporting needs, change velocity, and the cost of supporting complexity after launch.
We also favor recommendations that help projects remain portable. Where a capability is implementation-side, we prefer choices that can survive provider change. Where a capability is care-side and depends on managed processes, we make that distinction plain rather than hiding it in fine print.
When WordPress is the right platform, we still do not recommend components casually.
We avoid themes and plugins that are overly opinionated, difficult to follow, weak on extensibility, fragile under change, or likely to create unnecessary maintenance burden. Beautiful demos are easy. Clean long-term ownership is harder.
Theme and Foundation Shortlist
Our shortlist is intentionally small.
Astra is often a strong fit for many builder-driven projects and for projects that need a flexible starting point without excessive baggage.
GeneratePress is often a strong fit when theme discipline, performance, and cleaner foundations matter more than decorative excess.
Sage is often a strong fit for scratch-built projects that need a stronger development workflow and a more code-driven front end.
We are not claiming that these are the only worthy options in the market. We are saying that they commonly align with the kind of control, clarity, and maintainability we prefer.
Selected Component Categories
Some current examples of WordPress tools we commonly consider include the following:
Caching and performance: WP Rocket, plus Cloudflare-aligned strategies where appropriate
Custom fields and content structures: Meta Box
Forms: Gravity Forms
Commerce: WooCommerce
Events: The Events Calendar
Membership and learning: MemberPress and LearnDash
Search and filtering: SearchWP and FacetWP
SEO: The SEO Framework
Social media feeds: Smash Balloon
Static export: Simply Static
We also use page builders selectively rather than reflexively. Where a builder is appropriate, we choose with care. Where a code-driven or lighter-weight approach is the better long-term answer, we go that direction instead.
In other words, our WordPress recommendations are not “everything we have ever touched.” They are a narrowed set of tools that commonly pass our standards for fit, maintainability, and supportability.
Our recommendations are informed by more than vendor sales pages.
We pay closest attention to:
official documentation
changelogs and release notes
security advisories
accessibility and other standards guidance
vendor support history
practitioner experience that is concrete rather than theatrical
our own direct implementation, care, and troubleshooting experience
We generally trust official documentation first, direct experience second, and hype dead last.
This matters because good recommendations require evidence, not mood. Products change. Support quality changes. Pricing changes. Entire categories move from “good idea” to “maintenance headache” more quickly than many providers are willing to admit.
Good recommendations evolve.
Platforms improve. Platforms decline. Vendors get sharper. Vendors get sloppier. Update behavior changes. Support quality changes. Entire ecosystems shift underfoot. Anyone who pretends otherwise is either asleep or selling something too aggressively.
That is why this page should be read as a view into our current judgment, not as an unchanging list of eternal favorites.
What does remain stable is the standard behind the recommendations: maintainability, portability, standards fit, delivery maturity, practical usefulness, and commercial sense.
If you want the right stack for your organization, project, team, or engagement, the better move is not to copy someone else’s shopping list blindly. It is to choose against your actual goals, constraints, growth plans, and support model.
We can help with that.
