Marketeq Projects — Case Study

The Problem

The idea behind Marketeq Projects was simple: Buy a scoped service project → Choose your team → Launch.

But the actual experience wasn't that simple. The original version of the platform (pre-launch) tried to pack in a lot: editable scopes, team invites, pricing tiers, AI-generated deliverables. But without enough clarity or structure, During internal tests and early user flow reviews, we kept running into the same question: "Wait... what exactly am I committing to here?"

We weren't live yet, but we knew if we launched in this state, we'd lose trust before we even had a chance to build it.

✕ Problem 01: Scope Anxiety

Clients didn't feel confident editing their scope. There was no clear sense of what was included, how changes would affect the price, or whether edits would mess things up. It felt like building a contract blindfolded.

✕ Problem 02: Team Assembly Confusion

Inviting talent to a project sounds great, until you realize you don't know:

How many people are needed
What roles are already filled
Who you're actually hiring

There was no live status of open positions, and no reassurance that the project would still "work" if someone wasn't invited right away.

✕ Problem 03: The Checkout Cliff

The CTA said "Start Project," but most users weren't ready to start. There was no preview, no summary, no sense of what happens next. No financing options. No buyer protection. No safety net. And when people aren't sure... they don't click.

It kind of feels like I'm buying
a flight without seeing the destination.

👀 What We Noticed Early

We hadn't launched yet, but user feedback was already telling us this wasn't it. Even internal testers were stalling out, second-guessing their next step, or asking questions the UI didn't answer. That's when we knew we needed to redesign the whole experience before launching.

Design Requirements

🧊 Clarity Over Cleverness

Skip the cute labels. Ditch the jargon. We used plain language, phased sections, and clear bullets to help users instantly understand what they're getting.

"I need to know what I'm getting, not read a pitch deck." - Internal reviewer, early build

🛡 Build-In Trust, Don't Just Talk About It

Instead of just saying "safe," we showed it. We added creator bios, badges, refund policies, and secure payment indicators, all surfaced before checkout. This wasn't about decoration. It was about reassurance.

👁 Always Show What's Next

People don't freeze because they don't care. They freeze because they're unsure. So we broke down the flow into milestones, added previews, and used tooltips to explain things before they became questions.

💬 Keep the UX Calm

No pressure. No pushy CTAs. We made sure users could move at their own pace, with review screens, subtle prompts, and a checkout flow that felt optional until it wasn't.

Make Pricing Feel Predictable

Scope changes were allowed. Surprise pricing wasn't. We used dynamic price breakdowns, inline explanations, and "starting at" indicators to set clearer expectations, so edits felt flexible, not risky.

Design for the Unspoken Questions

Most users won't ask "Can I trust this?" They'll just leave if they're unsure. So we surfaced refund policies early, added reassurance tooltips, and placed reliability signals throughout the flow before users had to go looking for them.

The Solution

We didn't just patch the issues. We redesigned the whole flow.

We restructured the scope into editable phases, added real-time team visibility, and built a review-first checkout so users could actually see what they were committing to before clicking "Start Project."

Every change was meant to answer one question: "Do I understand what's happening, and do I feel okay moving forward?"

Here's what changed:

Clearer Pricing Signals

Starting prices were labeled as estimates, and any changes updated the cost in real time, no surprises.

Scope Previews

Clients could see exactly what each phase included, and how edits would impact the plan.

Live Team Status

A new status bar ("Need 4, Have 2") made it easy to track open roles, and removed the pressure to invite everyone upfront.

Klarna-style Checkout

We broke down total cost into digestible pieces, surfaced refund policies early, and added review screens before commitment.

Embedded Trust Signals

Creator bios, verified badges, and secure payment indicators were all placed intentionally, before users had to ask.

Contextual Tooltips

Instead of burying explanations in FAQs, we surfaced short, helpful tooltips right where users needed them most.

The result was a checkout flow where users actually knew what they were buying and felt good about clicking the button.

My Design Process

The same process runs through every project I take on. Learn, define, design, test, refine, then hand off. The loop from refine back to design is the part that matters most, because the first version of a screen is a hypothesis rather than an answer.

Design process: Learn, Define, Design, Test, Refine, then Dev Handoff, with an iteration loop from Refine back to Design. Each step lists its tasks below it.

Market Research

Comparing the Competition

Before finalizing any design decisions, we studied other marketplaces to understand how they handle the same problems we were trying to solve.

We analyzed a mix of direct and indirect competitors:

Upwork (freelancer-first, light on scope structure)
Fiverr (structured but rigid)
Themeforest (great spec breakdowns, product clarity)
Amazon, Etsy, Best Buy (e-commerce-level tooltips, trust layers, and purchase flow clarity)
Target, eBay, Epic Games (used for tooltip structure, "payment plan" transparency, and FAQs)

🔎 What We Were Looking For

Deliverable Clarity

How clearly are deliverables communicated?

Preview Accuracy

Can users preview exactly what they're buying?

Team Transparency

Is it easy to understand who's behind the service/product?

Checkout Confidence

Do users feel safe to check out?

✖ Where They Fell Short

🧱 Upwork & Fiverr

Deliverables are often just a few bullet points or marketing fluff
Hard to customize or understand what changes actually do
No clear invite logic for multi-person teams

🧩 Themeforest

Good specs... but no people. Just assets
No live team or service dynamics, not comparable, but worth stealing ideas from

💬 Amazon, Etsy, Best Buy

Surprisingly strong tooltip patterns
Clear policies, reviews, delivery estimates, but not designed for services

These gave us a model for how to explain complex scope info with simple overlays.

Competitor and e-commerce research board

Affinity Mapping

We gathered notes from interviews, internal feedback sessions, and early usability tests, and then we sat with it all to find the patterns.

It turns out, a lot of users were asking the same questions. Not always in the same words, but with the same energy:

Once we clustered everything, it became obvious: We weren't just solving for navigation or layout. We were solving for reassurance.

Common Themes We Found

💬 Trust + Transparency

"I need to know what I'm getting before I pay."
"What happens if the project doesn't go as planned?"

🧩 Scope Clarity

"This list of deliverables is overwhelming."
"Which part is editable vs. fixed?"
"What happens if I delete something by accident?"

👥 Team Assembly Confusion

"How many people do I need to invite?"
"What if I don't know anyone yet?"
"Can I finish checkout with just one person?"

💸 Checkout Hesitation

"Is there a way to split payments?"
"Where's the final review screen?"
"Can I cancel if I mess something up?"

💡 What This Told Us

People didn't want more options. They wanted fewer unknowns. So every feature from here on out, tooltips, trust badges, phased scope breakdowns, refund policies, was designed to answer one core question: "Is it safe to move forward?"

Affinity map: Clarity, Trust, Team Visibility, Checkout, Communication, and Browsing themes

Feature Prioritization

Once we had a clearer picture of what users needed, we mapped out every possible feature and sorted them by impact, effort, and emotional value. The question at the center of every decision: "Will this reduce doubt right before someone commits?"

If the answer wasn't a clear yes, it didn't make the cut.

✅ Must-Have

Editable phased deliverables
"Live Team Status" (e.g. Need 4, Have 2)
Trust badges and agency bios
Tooltips explaining scope, roles, and payment
Klarna-style financing breakdown
Purchase protection and refund policies

🤔 Nice-to-Have (Later)

Secret "auto-match" team mode
Creator DMs and floating chat widget
Real-time invite acceptance status updates
Version history for scope edits

❌ Will Not Have

Build-your-own-scope from scratch
Bulk/multi-project checkout
Tier comparisons and pricing tables
Cross-project reviews and deep creator stats

This helped us stay focused. We didn't chase "nice ideas." We prioritized emotional reassurance at exactly the point people tend to hesitate.

Card sorting: Best in Class / Out of Category

User Journey

We mapped out what it actually felt like to start a project on Marketeq, from browsing to checkout, and yeah... it got bumpy. Even in its pre-launch state, the journey was full of hidden stress points. People weren't just clicking buttons. They were hesitating. Guessing. Second-guessing. And sometimes? Just giving up.

💡 Where Things Got Messy

No clear overview before checkout
No visual on how many roles were still open
No hint that pricing was flexible or estimated
No emotional reassurance that it was okay to hit "Start"

😰 What We Had to Fix

To create a smoother, safer flow, we focused on the moments that triggered doubt and redesigned them with emotional clarity in mind:

Broke down the scope into editable, phase-based previews
Visualized team assembly in real time ("Need 4 / Have 2")
Added review steps and financing info before the final CTA
Layered in small trust signals: refund policies, verified badges, tooltips, and soft language

We weren't just mapping actions. We were mapping feelings. Because trust isn't built at the beginning or the end. It's built in all the little pauses in between.

Phase

1. Reviewing
Project Details

2. Editing
the Scope

3. Previewing
the Scope

4. Checkout

5. Invite Team
Members

6. Confirm
Availability

Emotions

Actions

1A. Decide if project fits needs, review details, and customize scope to liking.

1B. Search for transparency: deliverables, pricing, discount info, and budget details.

1C. Look for team info, FAQs, and Live Chat to ask questions before committing.

2A. Click to customize scope to reflect what they actually want out of the project.

2B. Try to change deliverables to match needs. Look for live price updates.

2C. Attempt to save progress. Worry about losing edits if tab closes.

3A. Review full scope before checking out. Confirm everything looks right.

3B. Check if everything is included. Look for edit and confirm buttons.

3C. Try to go back to fix a specific step without restarting.

4A. Begin purchase using preferred payment method.

4B. Double-check all payment and scope info before committing.

4C. Look for secure payment badges and summary before final click.

5A. Review suggested team members to fill open vacancies.

5B. Check candidate details one by one. Send invites to fill roles.

5C. Look for bulk invite option with talent details upfront.

6A. Wait for team members to accept or reject invites.

6B. Track invite status. Send more invites if needed.

Thoughts

1A. "I'd be less inclined to purchase if I'm too overwhelmed to read it."

1B. "I need to get it right the first time. I can't afford to start over."

2A. "I hope editing the scope won't be difficult."

2B. "I don't think I'd use this feature even though it's available to me."

3A. "I need to be confident the scope represents what I need."

3B. "I really hope I don't have to start all over."

4A. "I'd like to make sure I double check the payment since this is a HUGE sum of money."

5A. "This part feels like make or break."

5B. "I'm hoping the good talent saves enough time."

6A. "I don't want to keep checking to see if someone accepted. I have other things to do!"

Pain Points

1A. Project info is too overwhelming to read.

1B. Team is incomplete but I like the project. Don't know if I should go for it.

1C. Don't have funds to fix issues from miscommunication.

2A. Editing options are unclear or easy to miss entirely.

2B. Price changes unpredictably with no live feedback.

2C. No autosave if tab closes accidentally.

3A. Forgot to include something, wants to go back.

3B. Editing requires restarting from beginning.

3C. No seamless edit-and-return flow.

4A. Process feels too long.

4B. Questions platform legitimacy.

4C. No summary before final click.

5A. Too many candidates to check one by one.

5B. No clarity on why people were suggested.

5C. No bulk invite option available.

6A. No way to track who accepted or declined.

6B. "Available" talent not actually responding.

6C. Can't easily send more invites.

Insights /
Opportunities

1A. Organize info by sections for easier navigation.

1B. Explain team selection process clearly.

1C. Place key info in a singular, scannable section.

2A. Encourage "add to scope" over "remove."

2B. Show live price updates as scope changes.

2C. Add autosave or save-for-later feature.

3A. Allow editing specific steps without restarting.

3B. Preview should match final scope exactly.

3C. Make editing and preview seamless.

4A. Include payment and scope summary.

4B. Add double-check info before hitting checkout.

4C. Show secure payment indicators.

5A. Bulk invite with individual talent details.

5B. Show rate, skills, and availability upfront.

5C. Allow select-all or individual selection.

6A. Email alerts when invites are accepted.

6B. AI should factor confirmed availability.

6C. Require periodic availability updates from talent.

User Flows

We focused on redesigning the most emotionally loaded part of the platform: Buying a scoped project with a team.

This wasn't a typical e-comm flow. It wasn't "add to cart, check out." It was "do I understand what I'm buying, who I'm working with, and if I'm ready to commit?" So the flow needed to answer those questions, step by step.

Key Flow: Start to Checkout

Browse Project Scopes → View starting price, team type, and deliverables → Clear "Starting at $X" label with optional add-onsCustomize Scope → Add/remove phases, view dynamic pricing updates → Tooltip support for each deliverableInvite or Confirm Team → See who's needed, who's already included → Status indicator: "Need 4, Have 2" → Invite collaborators or proceed soloReview & Reassure → Klarna-style payment breakdown → Refund policy + team bios → Final scope preview before CTAStart Project (Or Don't) → Optional "Start Later" save state → Soft language on final CTA → Post-checkout confirmation: next steps, contact info, and edit options

Every step was designed to reduce friction, not just functionally, but emotionally. Because when people feel clear, they move forward. When they don't, they bounce.

Making something look simple is easy.
Making something simple to use is much harder.

Team matching and invitation user flow diagram

Legend

Wireframe Iterations

Project Header

The first version showed only the project title and vertical, no real context. We gradually added a breadcrumb, rating badge, and top-performer tags, then clarified the project name itself ("Custom iOS Marketplace App"). By V3, users knew what they were viewing, where it fit, and why it was credible, in just a glance.

Version 1

Version 2

Version 3

Pricing Sidebar with Team Info

In V1, the sidebar only offered time, price, and a "Start Project" CTA. By V2, we brought in visible team members and clearer formatting. V3 introduced flexible payment options ("$833/mo for 24 months") and embedded trust cues like refund terms, making the checkout feel more like a smart investment than a risk.

Version 1

Version 2

Version 3

Media / Gallery

The initial layout had a simple image placeholder. By V3, the gallery supported multiple content types, like videos and images, helping potential buyers better visualize what the project would look and feel like in action.

Version 1

Version 2

Version 3

FAQ / Live Chat / Question Form

V1 started with a basic "Ask a question" form. By V2, we added suggested questions and visible team availability. V3 introduced a live chat experience, complete with real-time presence (e.g. "Kevin is online") and expected response times. It turned a support feature into a trust-building moment.

Version 1

Version 2

Version 3

Final Features

Project Overview Header

This screen gives clients a clear, immediate snapshot of what they're looking at, from the project title and badges to pricing and trust markers. It sets the tone, builds credibility, and orients users before they even scroll.

Project Overview Info

Provides users with a quick snapshot of the project including title, ratings, sales count, and any badges, and a short description.

Project Description & Details

This section breaks everything down: what's included, how it works, who's involved, and what tools will be used, plus FAQs and reviews for added clarity.

Sidebar (Pricing, Team, CTA)

The sidebar surfaces essential info without making users hunt for it. Information includes cost, current team members, and project duration.

Peace of Mind Guarantee

Payment and refund policy is explained clearly right here for users. Clients know exactly what happens if things change.

Project Details

Designed to reduce uncertainty, this screen lays out everything from deliverables and tools to industries, tags, and team structure. It turns abstract project listings into concrete offerings users can actually evaluate.

Deliverables by Phase

Deliverables are broken down by project phase, so clients can see what to expect at each step.

Project Details

This section gives a full picture of the project's scope: tools and technologies involved, relevant industries, publish date, subcategories, and tags for quick filtering.

About the Team

Includes details on each member's skills, roles, location, languages spoken, and who's leading the project. Reassurance that the right people are already in place.

Final design: Project Details with deliverables, details, and team info

Questions

Whether users want to ask something directly, browse FAQs, or check response times, this screen makes it easy to get answers. It's a trust-building layer that meets clients where they are, unsure, curious, and looking for reassurance.

Ask a Question + Live Chat

Users can type and submit a question directly to the team, choose from suggested prompts, or chat live when someone's online.

FAQs & Recently Asked

This expandable FAQ section blends common questions with recent ones from other users. All responses come from the team, so info is always accurate and up to date.

Reviews

This screen balances the big picture and the personal, combining ratings summaries with actual feedback from past clients. It helps users validate their decision by showing how the project has performed for others.

Ratings Summary

A full breakdown of review scores plus the project's overall average and total number of reviews.

Individual Reviews

These reviews come from people who've actually purchased and completed the project.

Final design: Reviews with ratings summary and individual feedback

Browse Similar & Recommended

When users aren't ready to commit, this screen keeps them exploring. It offers curated paths forward, whether they want to compare similar scopes or browse intelligently recommended alternatives.

Final design: Similar and Recommended project carousels

Similar Projects Carousel

This carousel shows projects with similar scopes, industries, or tools, perfect for clients who want to compare before committing.

Recommended Projects Carousel

These recommendations are personalized based on what you're viewing, a quick way to discover projects with similar value or better alignment.

Related Categories

These clickable columns highlight categories connected to the one you're viewing, pulled from the project's main and subcategories to help users explore laterally without getting lost.

UI Design System

Every component in the final design is built from a unified design system I spent about two weeks building from the ground up. Colors, typography, buttons, tabs, and badges are all standardized to ensure visual consistency and speed up development handoff.

Stylized UI Components

Pricing Sidebar with Payment Plan, Team Status, & Guarantee

Anchored on the right side of the layout, this component keeps essential decision-making info visible and reassuring throughout the experience, from cost and team visibility to purchase protection.

Key Details

Klarna-style pricing breakdown shows the initial payment and flexible monthly options, so users know exactly what to expect financially
Current Team section displays real avatars and a "+X more" indicator, reinforcing that a qualified team is already in place
Start Project CTA is styled as a blue outlined button, visually prominent but not aggressive, paired with a note that additional payment plans are available
Peace of Mind Guarantee sits directly below the CTA with Purchase Protection and Trusted Transactions, giving users confidence that their money is safe

Together, these elements build a steady sense of clarity and control.

Pricing sidebar with payment plan, team status, and peace of mind guarantee

Media Player & Gallery

Turns the project offering into something clients can see and imagine, not just read about.

Key Details

Supports a mix of static images and video previews
Smooth carousel interaction lets users flip through visuals easily
Emphasis on clean framing and hierarchy to keep the experience elegant and informative

Media player with video playback and thumbnail carousel

Live Chat

A simple, direct way for users to message the project team when they have questions, no forms, no waiting, just a clear line of communication.

Key Details

Real-time presence indicator shows if a team member is online and available to chat
Familiar messaging interface keeps interaction lightweight and low-pressure
Designed to feel personal and responsive, even when the user just wants to clarify one small thing

Live chat interface with real-time messaging and online status

Scope Preview

This component gives users a clear, structured view of the project's original scope, broken down by phases, tasks, and team assignments, so they can understand exactly what they're buying before making changes.

Key Details

Organized by project phase for easy scanning and mental modeling
Each task includes a short description, assigned team member, and time estimate
Fully interactive and collapsible, so users can explore details at their own pace
Designed to reduce ambiguity and help users feel confident about what the current price includes, no edits, no surprises

Scope preview showing project phases, tasks, assignees, and durations

Hi Fi Designs

Project Overview

This screen was designed to give clients immediate clarity and confidence. The goal was to answer the big question "Is this the right project for me?" without making them scroll. I surfaced key details like project title, badges, pricing, and trust markers right away, paired with a visual gallery to build interest.

Bold badges, a muted layout, and a clear type hierarchy help draw attention to the most important details without the page feeling cluttered.

Questions

I knew that uncertainty often shows up as silence, so I wanted this screen to invite conversation. I integrated a live chat feature, suggested prompts, and a lightweight question form so users could get answers without friction. It was designed to feel more like texting a teammate than submitting a support ticket.

The online status ("Kevin is online") and average response time are small details, but they make it feel like there's a real person on the other end.

Questions screen with live chat, suggested prompts, FAQs, and ask a question form

Reviews

This screen goes beyond star ratings. I pulled in detailed reviews, visual summaries, and company responses so clients could understand why people felt the way they did, not just the score.

Avatars, icon-based tags (like "Highly Professional"), and clear spacing keep the reviews readable and scannable instead of overwhelming.

Similar & Recommended Projects

Not everyone is ready to buy right away, so this screen shows similar and recommended projects in a carousel. It lets clients compare options or switch directions without losing where they were.

Hover states and consistent thumbnail sizing keep the browsing experience clean and easy to scan.

Similar and recommended projects carousel with project cards, ratings, and team avatars

More Ways to Explore

This screen is for users who want to keep browsing. It shows related categories and search terms based on what they're already looking at, so they can find other options without going back to the main search.

The badge-style search suggestions and grouped categories give users a quick way to branch out without feeling lost.

User Testing

Before handing anything off, I ran moderated usability tests with 5 participants to validate the key flows. Each session lasted about 20 minutes and followed a structured test guide. I tracked completion rate, error rate, time to success, and satisfaction level, then assigned severity ratings (1 = cosmetic, 4 = must fix) to prioritize what needed attention.

5Participants

8Tasks Tested

91%Completion Rate

20 minAvg. Session

Task Results

Task	U1	U2	U3	U4	U5	Rate
Browse the project overview and identify what the project offers, who it's for, and the starting price.						5/5
Review the project scope, expand a phase, and understand what's included before editing.						4/5
Check the current team status and understand how many roles still need to be filled.						5/5
Ask the project creator a question using the live chat or suggested prompts.						4/5
Read reviews and determine if the creator is credible and trustworthy.						5/5
Find and compare similar projects without losing your place.						4/5
Complete the checkout flow and feel confident about the purchase decision.						1/5
Understand the payment breakdown and refund policy before committing.						4/5

Pass

Delayed

Failed

Key Findings

Severity 3Must Fix

Checkout Confidence

3 out of 5 users struggled with the checkout flow. Users wanted a review summary before final confirmation. We added a full review screen with scope, pricing, and team details before the commit step.

Severity 2Improve

Scope Navigation

1 user took extra time to locate the scope preview. We improved the "View Project Scope" label and added a visual indicator to draw attention to it.

Severity 1Cosmetic

Chat Discoverability

1 user initially missed the live chat entry point. We made the online status indicator more prominent and added a subtle pulse animation on first load.

Developer Handoff

I make sure developers understand every part of the interface. Every component has a master component with clearly defined variants, where all state management is laid out: default, hover, active, focused, and disabled states are all accounted for.

I prototype all key interactions so I can identify any missing states or edge cases before handoff. Then I organize every component variant side by side in a clean, structured layout so developers can reference them at a glance.

The design files are cleaned up and structured so the front-end functionality and detailed component architecture are immediately clear, no guesswork required.

Project Details

Modals

Modal components showing media player, authentication, and question overlays

Reviews

Rich Text Editor

Final Takeaways

This project taught me that making something work is only half the job. The other half is making people feel comfortable using it, especially when they're spending money and committing to a team. What started as "let's clean up this flow" turned into a full redesign. I'm glad we caught the problems before we shipped.

What I Learned

Just because something is functional doesn't mean it's reassuring.

If users don't trust the interface, it doesn't matter how well it works. Trust has to be designed in.

Users will always give better feedback than you expect, if you give them space to talk.

"Start Project" should never feel like a leap of faith.

What's Next

If I had more time (or dev resources), I'd love to explore:

Smart Invites

AI-powered team match suggestions based on role gaps and timeline.

Scope Simulation

Let users test changes before applying them.

Post-Checkout Invites

Let clients start with a core team, and fill in roles later without friction.

Saved Templates

Especially for agencies launching multiple projects at once.

All of these would keep building on the same idea: give users more information upfront so they can make better decisions faster. This project was never about adding features for the sake of it. It was about making the experience actually make sense.

Redesigning the project listing page to help clients buy with confidence

Designing for Reassurance

The Problem

✕ Problem 01: Scope Anxiety

✕ Problem 02: Team Assembly Confusion

✕ Problem 03: The Checkout Cliff

👀 What We Noticed Early

Design Requirements

🧊 Clarity Over Cleverness

🛡 Build-In Trust, Don't Just Talk About It

👁 Always Show What's Next

💬 Keep the UX Calm

Make Pricing Feel Predictable

Design for the Unspoken Questions

The Solution

Here's what changed:

Clearer Pricing Signals

Scope Previews

Live Team Status

Klarna-style Checkout

Embedded Trust Signals

Contextual Tooltips

My Design Process

Market Research

Comparing the Competition

🔎 What We Were Looking For

Deliverable Clarity

Preview Accuracy

Team Transparency

Checkout Confidence

✖ Where They Fell Short

🧱 Upwork & Fiverr

🧩 Themeforest

💬 Amazon, Etsy, Best Buy

Affinity Mapping

Common Themes We Found

💬 Trust + Transparency

🧩 Scope Clarity

👥 Team Assembly Confusion

💸 Checkout Hesitation

💡 What This Told Us

Feature Prioritization

✅ Must-Have

🤔 Nice-to-Have (Later)

❌ Will Not Have

User Journey

💡 Where Things Got Messy

😰 What We Had to Fix

User Flows

Key Flow: Start to Checkout

Wireframe Iterations

Project Header

Version 1

Version 2

Version 3

Pricing Sidebar with Team Info

Version 1

Version 2

Version 3

Media / Gallery

Version 1

Version 2

Version 3

FAQ / Live Chat / Question Form

Version 1

Version 2

Version 3

Final Features

Project Overview Header

Project Overview Info

Project Description & Details

Sidebar (Pricing, Team, CTA)

Peace of Mind Guarantee

Project Details

Deliverables by Phase

Project Details

About the Team

Questions

Ask a Question + Live Chat

FAQs & Recently Asked