Process

A clear process for websites, apps, AI, and custom systems.

Every project starts with understanding the real business need. From there, WGP defines the right scope, designs the experience, builds the system, tests the details, launches carefully, and can remain involved after release.

The exact process is adapted to the project — a focused website does not need the same architecture as a portal, healthcare integration, or mobile application.

The seven phases

From understanding the problem to supporting the launch.

Each phase adapts to the project. Some are lightweight for a focused website. Others expand significantly for portals, mobile products, healthcare systems, and regulated environments.

  1. Phase 1

    Understand the business and the real problem.

    WGP begins by learning how the business works, who the users are, what is already in place, what is creating friction, and what the project needs to accomplish.

    Activities

    • Business and user goals
    • Existing website or system review
    • Customer and employee workflows
    • Current tools and integrations
    • Content and asset review
    • Technical constraints
    • Security and privacy considerations
    • Future growth needs

    Client involvement

    You provide the business context, priorities, current tools, available content, and the people who should be involved in decisions.

    For healthcare or regulated workflows, this phase also identifies data sensitivity, access requirements, vendors, agreements, and compliance responsibilities.

  2. Phase 2

    Define the right scope before building.

    The project is translated into a clear recommendation covering pages, features, workflows, integrations, responsibilities, timeline, and pricing.

    Activities

    • Project scope
    • Feature priorities
    • Page and content plan
    • User roles and permissions
    • Integration requirements
    • Technical approach
    • Milestones and dependencies
    • Proposal and payment structure
    • Out-of-scope boundaries

    Client involvement

    You review the proposed direction and confirm that the scope solves the right problem before major build work begins.

    A focused project with a clear scope is more valuable than a larger build filled with unnecessary features.

  3. Phase 3

    Design the experience before final development.

    WGP shapes the structure, customer journey, interfaces, content hierarchy, and visual system so the project is understandable before it is fully built.

    Activities

    • Site maps and user flows
    • Page and screen structure
    • Content hierarchy
    • Wireframes where useful
    • Visual direction
    • Responsive layouts
    • Forms and interaction design
    • Dashboard and portal interfaces
    • Mobile and hybrid iOS considerations
    • Accessibility-conscious design

    Client involvement

    You review real page or screen direction, provide focused feedback, and approve the experience before the project moves deeper into development.

    Review stages are defined in the project scope.

  4. Phase 4

    Build the website, application, or system.

    WGP develops the approved experience and connects the technical pieces required for the project to function.

    Activities

    • Responsive website development
    • Web application development
    • Hybrid and native iOS development
    • Capacitor integration
    • Native plugins and bridges
    • Database and backend development
    • Authentication and permissions
    • Portals and dashboards
    • Stripe and payment connections
    • Plaid integrations
    • Epic and healthcare APIs
    • FHIR-based data workflows
    • Apple Health integrations
    • CRM and third-party APIs
    • AI tools and automation
    • Browser and Playwright workflows
    • Admin and operational controls

    Client involvement

    You review working milestones, answer business-rule questions, and provide access to approved vendors, systems, accounts, or APIs when needed.

  5. Phase 5

    Test the details and strengthen the system.

    Before launch, WGP reviews functionality, responsive behavior, integrations, permissions, failure states, data handling, and the overall user experience.

    Activities

    • Desktop and mobile testing
    • Form and workflow testing
    • Integration testing
    • Authentication and permission review
    • Error and empty states
    • Cross-browser checks
    • Accessibility review
    • Performance review
    • Backup and recovery considerations
    • Logging and audit trails
    • Encryption and secrets handling
    • SiteScope crawl and visual review
    • App-device testing where applicable
    • HIPAA-ready architecture review (for regulated systems)
    • SOC 2-aligned control review (for regulated systems)
    • Least-privilege access
    • Audit logging
    • Privacy and consent workflows
    • Vendor and infrastructure considerations

    Client involvement

    You review test findings, prioritize fixes, and confirm the system behaves the way the business needs before launch.

    Compliance depends on the complete technical environment, policies, vendors, agreements, operations, and audit process. WGP can build the technical foundation and controls needed to support those requirements.

  6. Phase 6

    Launch carefully, not abruptly.

    WGP prepares the project for production, verifies the final configuration, and coordinates the technical steps required to release it.

    Activities

    • Domain and DNS connection
    • Hosting and deployment
    • SSL configuration
    • Redirect planning
    • Production environment setup
    • Final content review
    • Analytics and indexing setup
    • Form-delivery verification
    • Payment and integration checks
    • App Store preparation where applicable
    • Release and rollback planning
    • Final launch review

    Client involvement

    You approve the final release, provide any remaining production credentials or account access, and confirm the business is ready to receive users, leads, payments, or data.

  7. Phase 7

    Support the launch and keep improving.

    WGP can remain involved after release through hosting, maintenance, monitoring, routine updates, product support, and future development.

    Activities

    • Managed website hosting
    • Security and software updates
    • Routine backups
    • Minor website edits
    • Form and integration checks
    • Bug fixes
    • Product updates
    • App release support
    • SiteScope review
    • Analytics and feedback review
    • New feature planning
    • Major improvements quoted separately

    Client involvement

    You report business changes, user feedback, new priorities, and issues that should guide future updates.

    Routine support and minor website edits may be covered by an ongoing care plan. New pages, major redesigns, new modules, and substantial functionality are scoped separately.

The process adapts

Different projects need different levels of planning and testing.

The project proposal identifies which phases and deliverables apply before work begins.

Business Website

Typical emphasis

  • Content and page structure
  • Visual design
  • Lead forms
  • SEO foundations
  • Responsive testing
  • Domain and launch setup
  • Hosting and care

Integrated Website

Typical emphasis

  • Booking
  • Payments
  • CRM connections
  • Lead routing
  • Third-party APIs
  • Workflow testing

Custom System or Portal

Typical emphasis

  • User roles
  • Permissions
  • Dashboards
  • Data workflows
  • Business logic
  • Admin controls
  • Security and audit logging

App, AI, or Regulated Product

Typical emphasis

  • Product architecture
  • Mobile behavior
  • APIs and integrations
  • AI workflows
  • Offline and background processes
  • Security controls
  • Healthcare interoperability
  • App Store release
  • Ongoing product support

Your role

Good projects move faster when decisions and access are clear.

Every project is collaborative. A few things from your side keep the work focused and the timeline predictable.

Business knowledge

You understand the customers, services, workflows, priorities, and operational realities the system needs to support.

One decision path

Define who can approve scope, design, content, and launch decisions.

Content and assets

Provide available text, images, brand materials, legal language, and business information — or identify where WGP should help.

Platform access

Provide approved access to domains, hosting, Stripe, CRM systems, Epic or healthcare environments, analytics, Apple accounts, and other required tools.

Timely feedback

Review milestones and return clear, consolidated feedback within the agreed project rhythm.

Compliance ownership

For regulated systems, the business remains responsible for legal, policy, operational, vendor, and audit obligations while WGP supports the technical implementation.

Communication

Clear communication throughout the build.

Projects are organized around defined milestones, visible progress, focused review points, and documented decisions. The exact communication rhythm is established in the proposal based on the size and complexity of the work.

  • Defined milestones
  • Clear owners
  • Consolidated feedback
  • Documented scope
  • Approval checkpoints
  • Early visibility into working designs or builds
  • Out-of-scope approval before additional work

FAQ

Common questions about how projects work.

Does every project follow all seven phases?

No. The process is adapted to the work. A focused business website may move through planning, design, build, testing, and launch quickly, while a portal, mobile app, healthcare integration, or AI product requires deeper architecture and testing.

How long does a project take?

Timing depends on scope, content readiness, integrations, technical complexity, review speed, and launch requirements. The expected timeline is defined in the proposal before work begins.

How involved do I need to be?

WGP handles design and development, but the client provides business knowledge, access, content, decisions, and timely feedback. The process is structured so involvement is focused at the moments where it matters most.

Can the scope change after work begins?

Yes, but new work is discussed before it is added. Changes that affect pages, features, integrations, architecture, or timeline are scoped and approved separately.

Will I see the project before launch?

Yes. Review points are built into the project so you can see and respond to the direction before final release.

Do you test mobile and desktop?

Yes. Websites and web applications are reviewed across responsive layouts. Mobile and hybrid iOS products also require device-specific testing based on the project.

Can you work with Epic and healthcare systems?

Yes. WGP can build healthcare API integrations, FHIR-based workflows, Epic-connected experiences, Apple Health connections, and secure patient or provider data workflows when the required access, vendor agreements, and technical environment are available.

Can you build for HIPAA and SOC 2 requirements?

WGP can design HIPAA-ready architecture and SOC 2-aligned technical controls, including permissions, encryption, audit logs, secure integrations, and privacy workflows. Complete compliance also depends on policies, operations, vendors, agreements, and independent legal or audit review.

What happens after launch?

WGP can provide hosting, maintenance, routine edits, monitoring, bug fixes, integration support, app updates, and future development. The exact support coverage is defined separately.

Have a project that needs more than a generic agency process?

Tell us what you are trying to build. WGP will help define the right scope, process, architecture, and path to launch.