Architecture context
Capture systems, goals, constraints, risks, stakeholders, dependencies, and existing architecture decisions in a more structured form.
Meridian access
Request guided access to Meridian.
Meridian is Resolving Architecture’s product for architecture evaluation, decision capture, governance, and implementation alignment. Access is currently guided so the product can be matched to real architecture evaluation and governance needs.
Who should request access
Meridian is intended for teams with real architecture decisions to govern.
Meridian is a fit when your team needs to evaluate architecture context, identify consequential decisions, capture rationale, preserve an architecture baseline, or monitor implementation against accepted decisions.
Access may be appropriate for CTOs, founders, architecture teams, platform teams, principal engineers, and engineering leaders working through modernization, integration, reliability, governance, or architecture drift concerns.
Evaluation focus
What guided access can help evaluate.
The first conversation is usually about whether Meridian fits your architecture workflow and what kind of architecture context you want to make more explicit.
Decision discovery
Identify which choices are architecture decisions requiring rationale, ownership, trade-off visibility, and stakeholder understanding.
Architecture baseline
Establish a durable record of accepted architecture intent, constraints, decisions, assumptions, and implementation guardrails.
Governance workflow
Evaluate how architecture decisions should be reviewed, recorded, revisited, and connected to implementation activity.
Implementation alignment
Explore how future delivery work can be monitored against the accepted architecture baseline so drift becomes easier to see.
Consulting fit
Determine whether Meridian should be used independently, through a guided evaluation, or alongside focused Resolving Architecture consulting.
Phase 1 pricing
Meridian services are priced by outcome.
Phase 1 pricing is available for Document, Evaluate / Review, and Evaluate Intermediate. Other Meridian services will be available in future versions.
Meridian uses product-style pricing because these services are repeatable, product-supported outcomes. Custom architecture consulting is scoped separately when direct senior judgment, organizational context, or recurring fractional support is needed. Consulting can stand alone, while Meridian is the preferred continuity layer when decisions need to be captured, governed, or revisited over time.
Document
$299
Create a clearer written record of architecture context, decisions, rationale, assumptions, constraints, and implementation guidance.
Evaluate / Review
$499
Review architecture context, risks, trade-offs, dependencies, and alignment with business, technical, delivery, and operational goals.
Evaluate Intermediate
$199
Review a focused change or implementation question against an existing architecture baseline.
Founding Design Partner Beta
Get discounted Meridian access while helping make the product ready for use.
Founding design partners receive discounted access to Meridian Phase 1 services for 90 days in exchange for active product feedback and real or representative architecture usage.
Document
$149 beta
Evaluate / Review
$299 beta
Evaluate Intermediate
$99 beta
Beta participants agree to use Meridian on real or representative architecture work, provide feedback after completed reviews, and participate in at least one feedback conversation. Meridian may use feedback and anonymized usage signals to improve the product and may publish aggregated, non-identifying learnings.
Meridian will not publish your company name, logo, confidential architecture content, source material, or identifiable project details without your prior written approval.
Customers who agree to participate in an approved anonymous or named case study may be eligible for additional beta discounts or service credits. No case study will be published without customer review and approval.
Request beta accessBefore sharing details
Architecture context can be sensitive.
Initial access requests do not need to include confidential system details, source code, security information, customer data, incident details, or proprietary architecture materials.
Start with the type of decision, governance need, or architecture challenge you want Meridian to help with. Confidentiality, data handling, and review boundaries can be discussed before any detailed architecture materials are shared.
Request access
Send a short note about what you want Meridian to help govern.
Include your name, organization, role, and the architecture decision or governance concern that prompted your interest. If you are interested in the Founding Design Partner Beta, select that as the topic and mention that interest in the note.
Access may be limited while Meridian is evaluated with teams whose needs are a good fit for architecture governance, decision capture, and implementation alignment.
Request Meridian access