Strategy · the Azteya method
Built for the US market, the way US customers actually buy.
One process applied across every service. Discovery, positioning, build, launch, improve. Same shape every engagement so the work is predictable and the result is repeatable.
The five phases
We don't start designing until the brief is real. We don't launch until the gates pass.
-
01
Discovery
Goal
Build a brief that's specific enough to design against. Audit current state, understand the audience, surface real friction.
What we do
- Stakeholder interviews (sales, support, leadership)
- Current site, traffic, search, and analytics audit
- Competitor & reference review (US-market specific)
- Buyer-journey + objection map
-
02
Positioning
Goal
Sharper claims, audience-first message, US-market context, proof hierarchy. Make the trust-in-3-seconds test pass.
What we do
- Primary message + audience/outcome statements
- Sitemap + page priorities
- Proof hierarchy (logos, screenshots, metrics, quotes)
- One primary CTA, one scheduling route
-
03
Build
Goal
Production-grade work that hits performance, accessibility, and SEO targets before it ships. Editable by your team after.
What we do
- Tokens-first design system (color, type, spacing, motion)
- Component-based templates your team can edit
- Schema, sitemap, internal links, AEO answer blocks
- Core Web Vitals + accessibility budgets enforced
-
04
Launch
Goal
No surprises on day one. Redirects clean, analytics firing, monitoring on, team trained.
What we do
- 301 redirects from every old URL we can find
- GA4 + Search Console + tag-manager events tested
- Cross-browser, mobile, accessibility QA pass
- Team training + handoff doc
-
05
Improve
Goal
A 90-day improvement loop on real data. Then quarterly. The site keeps earning instead of decaying.
What we do
- Monthly performance + visibility report
- A/B tests against the highest-leverage pages
- Content additions tied to real buyer questions
- Quarterly executive read-out
Built for the US market
Where this method differs from a typical agency build.
- US-customer language, not translation
- We write the English version first, with idiom and tone calibrated for US buyers. Then we localize Spanish where it serves a real audience, not as a checkbox.
- Bilingual operations, US accountability
- Registered as a US LLC. Bilingual team across Mexico and the Dominican Republic, working US business hours, with US-market knowledge baked into recommendations.
- Trust cues calibrated to the audience
- SOC posture, privacy posture, contract clarity, response-time SLAs, transparent pricing, the proof signals US buyers actually look for, not the ones agencies usually copy from each other.
- Compliance-aware forms & flows
- Privacy policy & terms updated, cookie disclosure where relevant, data retention defaults, opt-out paths, done by default, not as a post-launch fire drill.
- Acceptance gates, not "we'll polish in production"
- Each phase has a written gate. Performance, accessibility, copy clarity, anti-pattern checks. We don't ship past a failing gate.
Quality gates
What "done" actually means.
Accessibility
WCAG 2.2 AA: alt text, headings, focus, contrast, keyboard, reduced motion, error text, form labels.
Performance
LCP ≤ 2.5s · INP ≤ 200ms · CLS ≤ 0.1 at 75th percentile. Hero video optimized and non-blocking.
Responsive
Mobile-first, no two-axis scroll, reachable nav, touch targets ≥ 24px, readable at 320px.
Anti-patterns
No invented logos, no fake metrics, no stock-photo team, one CTA per section, differentiated copy.
Apply the method to your project