Build with discrete, supportable, and swappable Features for realistically implementable scope, structure, maintainability, portability, and growth.

Select and assemble Web, AI, Marketing, Product Management, DO/IT, and Coaching Features in virtually any project.

What a Feature Actually Is

A Feature is a discrete package of capability. It is not merely a description of something an app does or a behavior a site exhibits. Rather, it is a clearly described unit of functionality that can be demonstrated, implemented, tested, documented, priced, and supported with discipline.

This is significant because serious projects don't fail only on code, content, or design. They also fail on ambiguity. When delivery is wrapped in clear Features, scope becomes easier to define, responsibilities become easier to understand, pricing becomes easier to follow, and future changes become easier to manage without damaging the working relationship.

All deliverables across all six EhvenConsultants Areas of Interest (our AOI's) are assembled from one or more Features. That is how we keep the work legible, portable where appropriate, and commercially sane.

The Seven Parts of Every Feature

Every Feature is built from the same structural pattern:

Capability Matrix explains the Feature clearly and allows us to select together only the capabilities that are actually needed for the project (avoids bloat, reduces complexity, and focuses spending).
Build Package contains the materials required to implement it.

Test Suite defines how the Feature is validated.
Success Kit supports project-side stakeholders and users.
Operations Kit drives administration and operation of the Feature and its effects on stakeholder goals.
Care Kit supports the ongoing environments, processes, and routines required for qualified care.
Pricing Pair defines the one-time implementation price and the ongoing care price.

This structure affords clients a clearer buying model, empowers teams a cleaner delivery model, and provides future providers a better chance of understanding what was actually built instead of effectively requiring them reverse-engineer intent from a mess.

Feature Types, Pricing, and Portability

Features are delivered in four primary types: Base Implementation, Base Care, Addon Implementation, and Addon Care.

Base Implementation Features are integrated into a project or engagement once, whether at initial implementation or through a later CR (change request). They establish the baseline, do not carry additional per-Feature charges, and remain with the implementation even if the project later moves to another provider.

Base Care Features support a project or engagement on an ongoing basis. They are part of the care relationship rather than part of the implementation itself. Because they depend on our own environments, operating routines, tooling, and internal processes, they generally do not move with the project when it exits our ecosystem (though custom implementations are available for some of these Features that are not dependent upon our ecosystem, and these can be requested upon exit).

Addon Implementation Features are also integrated into the implementation itself, but they extend the baseline and may carry additional per-Feature costs. Like other implementation Features, they remain with the project when it moves.

Addon Care Features expand the care relationship rather than the implementation itself. They may carry additional per-Feature costs, and they generally do not travel with the project because they depend on our own care systems, environments, and workflows (here, again, custom implementations are available for some of these Features that are not dependent upon our ecosystem, and these can be requested upon exit).

Select care-related capabilities that are made available upon exit, whether for purchase or subscription, commonly require project-specific adaptation rather than a traditional handoff.

Every Feature also uses a Pricing Pair. That means there is always a one-time implementation price and, where applicable, an ongoing care price. When work is exploratory, highly customized, or R&D-heavy, it may instead be handled through the hourly version of the Pricing Pair in a separately scoped custom strategy, delivery, or engineering effort.

Core Features and Superchargers

Most Base Features are Core Features. Core Features do the essential job, often quite minimally. They establish the baseline capability that a serious project or engagement should have before anyone starts piling on extras.

Many Core Features can then be expanded by Supercharger Features (which are always Addon Features). Superchargers do not replace the baseline. They deepen it, extend it, harden it, or make it more ambitious where the project genuinely benefits from the added investment.

That structure helps clients avoid two common mistakes. The first is underbuilding by skipping fundamentals. The second is overbuying by funding advanced machinery before the baseline is even stable. Core first. Supercharge where it earns its keep. This is a better way to build.

Six Areas of Interest

Our current Feature catalog is organized into six Areas of Interest.

Web covers the implementation and care of serious web platforms and experiences, including accessibility, design systems, search, policy layers, performance, security, SEO and AIO, data structures, content flows, and reliability-focused care.

AI covers practical AI delivery, governance, grounding, retrieval, agents, prompting, guardrails, quality control, and ongoing tuning and review.

Marketing covers audience definition, offer framing, campaign systems, content systems, channel setup, visibility, analytics, review management, optimization, and the supporting structures that turn activity into actual business movement.

Product Management covers goals management, requirements gathering and translation, queues, roadmaps, research, discovery, prototyping, analytics, optimization, and the planning structures required to move from wishful thinking to usable decisions.

DO/IT (which stands for "Digital Operations IT") covers the operational layer: Access, release, recovery, logging, DNS, email, Cloudflare, migration, vendor liaison, and the other realities that keep serious projects from collapsing under their own dependencies.

Coaching covers structured education, enablement, implementation support, adoption support, decision support, practice development, and follow-through for individuals and teams that need more than theory.

This catalog structure keeps ownership clear without pretending that real projects are ever perfectly isolated by discipline.

Cross-AOI Scoping Is Normal

Every Feature lives entirely within a single Area of Interest, even when it supports work in more than one area, or for multiple project scenarios or types. This is deliberate. It keeps responsibilities anchored where they most naturally belong.

A Web project, for example, may rely on DO/IT release and recovery Features. An AI project may rely on Web for dashboards or the like, Product Management for roadmapping, or Marketing for social media advertising. A Coaching engagement may rely on AI for Agentic research or Product Management for adoption support, planning, or execution. This is all normal. It mirrors the real delivery world, where strong outcomes usually depend on more than one discipline.

In select cases, a Feature has distinct versions across multiple Areas of Interest because the operational reality is materially different from one AOI to another. Incident response is a good example. Sometimes a shared Feature is the right answer. Sometimes separate per-AOI versions are the better answer. We choose the cleaner model, not the buzzier one.

Feature List

Current catalog coverage includes work such as:

Web Features for accessibility, analytics, APIs, comments, design systems, performance tuning, policy pages, search, security, style guides, syndication, backups, compatibility testing, database optimization, uptime monitoring, SRE, and a wide range of implementation extensions.

AI Features for readiness, strategy, semantic search, knowledge flow, agents, model routing, prompt frameworks, guardrails, lab review, regression testing, reporting, and ongoing tuning.

Marketing Features for audience definition, offer framing, research, strategy, copywriting, content programs, email and SMS programs, channel starters, analytics, search visibility, review management, and conversion optimization.

Product Management Features for goals and success metrics, requirements, queues, roadmaps, research, discovery, feasibility, prototyping, analytics, performance monitoring, and progress reviews.

DO/IT Features for access control, release operations, recovery, backups, logging, DNS health, domain management, Cloudflare and other perimeter options, email deliverability, vendor liaison, contributor onboarding, and emergency response.

Coaching Features for orientation, action planning, resource packs, office hours and live fire exercises, progress review, implementation support, AI adoption, workflow design, delivery systems, and team-level capability building.

If you already know what you need, this list should help us start planning together. If you don't, it should still give you a cleaner starting point than a vague shopping list or a wish cloud.

Start with the Right Mix

Not every project needs every Feature. More Features does not automatically mean better delivery. Good scope starts with the right baseline, adds power where it is justified, and keeps care obligations honest from the beginning.

That is one reason we organize the catalog the way we do. It helps serious buyers, project owners, and hiring stakeholders separate essentials from expansions, implementation from care, and portable value from provider-dependent service layers.

If you already know the Features you need, we can help you scope, sequence, and price them properly. If you don't, we can help you identify the right initial mix without turning the process into guesswork, theater, or invoice roulette.