- Platform. Webflow CMS, Ecommerce and native forms, plus resident portals (FRONTSTEPS, Property Pay) the site links to but doesn't control.
- Legal. Texas Property Code §207.003 sets resale-certificate delivery at 10 business days (7 for updates), caps fees and limits when payment can be processed.
- Audiences. Boards evaluating, residents seeking help and professionals ordering documents were all landing on the same pages.
Triquest Management Website
Rebuilt a Houston HOA management firm's digital presence on Webflow, then led an audit-driven optimization round across service design, conversion and accessibility.
[ SYS_STAT ]
CLIENT
TriQuest Management
SECTOR
Property Management
YEAR
2025–2026
ROLE
Visual Strategy Lead · Product Design & Webflow
DELIVERY
10-wk relaunch + audit round
proc_uptime 00:00:21
Strategic Brief & Constraints
01
> run brief.txt
TriQuest's legacy WordPress site went offline, leaving a Houston HOA management firm invisible to the boards it wanted to win and hard to reach for the residents it already served. I led the relaunch on Webflow in 10 weeks, then returned in 2026 to audit the live site and run a focused optimization round.
The brief was bigger than a new look. One site had to sell to volunteer boards, support homeowners, and handle legally regulated document orders from realtors and title companies, without the three getting in each other's way.
[ DELIVERABLES ]
›
UX Audit & Service Design
›
Visual System & Accessibility
›
CMS & Content Architecture
›
Webflow Development
›
Automation & Form Routing
›
SEO, Analytics & Localization
[ 01 ]
Constraints
[ 02 ]
Audience
HOA board members choosing a management firm · Homeowners paying dues and looking for help · Realtors, title companies and lenders ordering closing documents
[ 03 ]
Discovery Inputs
Heuristic UX audit · Content inventory (26 pages, 3 CMS collections) · Texas Property Code review · Stakeholder goals
[ KEY INSIGHTS ]
01
Proof over promises: 18 unverified statistics across six service pages became process facts a board can check, like monthly financial reports and quarterly CPA reviews.
02
Ask less, earlier: a first proposal request should be finishable on a phone in a few minutes. Details like finances and access codes belong in the first conversation.
03
Every page needs a next step: success and error messages now say what happens next and offer a direct line, instead of leaving visitors at a dead end.
Architecture & Service Design
02
[ INFORMATION ARCHITECTURE ]
Structure before surface
The original site served every visitor from the same pages, which is why boards met resident notices and title companies hunted for closing documents. I restructured the architecture around three audience branches, so each group reaches its task in one or two clicks from the homepage.
The branches shipped in three places. Three audience paths sit directly below the homepage hero. The main menu follows the same model: a Services mega menu that explains each service and ends in “Request a Proposal”, and a Resources menu that puts dues, the resident portal and FAQs first, with closing documents one click away. The document shop opens with a three-step “How ordering works” guide above the catalog. Next on the roadmap is a dedicated resident hub.
Service flow: ordering a resale certificate
Mapping who acts at each step exposed what a page audit never would: charging at checkout may conflict with §207.003, which limits when a resale-certificate payment can be processed. I flagged the risk and brought the payment question to the client before anything went live.
That question is still open. My recommendation, prototyped in Figma: authorize the card at checkout and charge it only when the certificate is ready, pending client and legal review.
[ RESEARCH ARTIFACTS ]
No items found.
Conversion & UX Optimization
03
[ KEY UX DECISION ]
Board members were asked for gate codes, delinquency rates and annual assessments before anyone had called them. I cut the form to one step and nine fields, five of them required, fixed mismatched labels and input types, and replaced the generic thank-you with a clear next step and a phone number.
[ SIGNAL 01 ]
DESIGN SIGNAL
Proof over promises: 18 unverified statistics across six service pages became process facts a board can check, like monthly financial reports and quarterly CPA reviews.
[ SIGNAL 02 ]
DESIGN SIGNAL
Ask less, earlier: a first proposal request should be finishable on a phone in a few minutes. Details like finances and access codes belong in the first conversation.
[ SIGNAL 03 ]
DESIGN SIGNAL
Every page needs a next step: success and error messages now say what happens next and offer a direct line, instead of leaving visitors at a dead end.
Visual System & Accessibility
04
Font Selection
Manrope Bold
Heading Selection
Manrope Medium
Subheading Selection
Manrope Regular
Paragraph Selection
The visual system paired restrained typography and reusable Webflow components with targeted accessibility fixes. Correcting one shared component repaired 53 screen-reader button labels; shared contact links became tappable site-wide; a compact phone pattern and responsive headline sizes improved small-screen use. The work targets WCAG 2.2 AA, with full contrast and keyboard audits still pending.
Color Palette
[ TOKEN: PRIMARY ]
#030abc
[ TOKEN: SECONDARY ]
#f2b705
[ TOKEN: SURFACE ]
#232323
[ TOKEN: GRAY ]
#9c9c9c
[ TOKEN: NEUTRAL ]
#f6f7f9
[ TOKEN: WHITE ]
#ffffff
Logo
[ mockups / screens / states ]
No items found.
- One fix, 53 buttons. The animated button component made screen readers announce every label twice. Hiding the decorative copy inside the component corrected all 53 instances at once.
- Tap to call. Phone numbers and emails in the shared contact block became real links, fixing every page that uses it in a single edit.
- Built for thumbs. A compact nav variant keeps “Request a Proposal” on one line on phones, and the headline steps down from 3.75rem to 2.75rem across breakpoints.
- WCAG 2.2 AA targets. Labels match their inputs, fields use the right input types, and the SMS popup waits 30 seconds and stays dismissed for 30 days.
Outcomes & Technical Handoff
05
BUILD_LAUNCH_OUTCOME.log
[ BUILD 01 ]
CMS & Content Architecture
[ BUILD 02 ]
Webflow Development
[ BUILD 03 ]
Automation & Form Routing
[ BUILD 04 ]
SEO, Analytics & Localization
[ IMPLEMENTATION NOTE 01 ]
The service template was rebound to each item's own CMS fields, replacing a generic heading and a paragraph repeated across five pages, so every service page updates from one place.
[ IMPLEMENTATION NOTE 02 ]
Forms route automatically by intent, the Spanish locale is in place, and every change was staged and kept reversible (replaced elements hidden, not deleted) so the client reviews one release before it goes live.
- 4 → 1 Proposal form steps
- 14 → 9 Form fields (5 required)
- 53 Buttons fixed for screen readers with one component change
- 18 → 0 Unverified claims on service pages
How success will be measured
- Proposal requests per month and form completion rate
- Share of document orders that arrive with complete property details
- Calls and emails about payments and portal access, before and after launch
- Mobile taps on “Request a Proposal” and the phone number
Tracked at 30, 60 and 90 days after launch.
“We needed a digital presence that built trust fast.”
The relaunch restored that presence. The optimization round made it easier to act on.
No items found.
[ Navigation ]
06
[ Contact ]
07
[ CONTACT ]
[ Start Project ]
[ RESPONSE WITHIN 48 HRS ]
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
