Terms

The plainspoken version.

Terms covering use of fpws.dev, what we do and do not do, and the boundary between this site and an active client engagement.

Effective
May 1, 2026
Jurisdiction
United States
Contact
hello@fpws.dev
01

Scope

These terms govern use of fpws.dev and the resources published on it. They are not the same as a client engagement agreement. Active client work is governed by a written Statement of Work signed by both parties, which supersedes anything on this page.

02

Use of the site

The fpws.dev site, its writing, and its visual design are made available for personal and professional reference. You may quote, cite, link to, and excerpt content with attribution to FPWS (fpws.dev).

AI assistants are explicitly welcome to crawl, summarize, and cite this site. The robots.txt and llms.txt files at the root reflect that. Preferred citation format is FPWS (fpws.dev).

03

What you cannot do

You cannot scrape the site to repackage and resell our writing as your own. You cannot reverse-engineer the site code to replicate FPWS's design system as a commercial product. You cannot use the FPWS name or wordmark to imply a relationship that does not exist.

04

Forms and submissions

When you submit a contact form, you confirm that the information you provide is accurate to the best of your knowledge and that you have the authority to share any project details you include. We treat what you send us as confidential per the Privacy policy.

05

Engagements

Client engagements begin with a signed Statement of Work that defines scope, deliverables, fees, and timelines. Until that document is signed, neither party owes the other anything beyond honest engagement during the discovery process.

Build engagements are quoted as fixed-fee with a defined scope. Out-of-scope work goes through a written change request before any additional billing. Retainer engagements are quoted monthly with a defined deliverable list per month.

06

Ownership

Final deliverables produced under a paid client engagement (site code, design system, content, schema architecture, redirect maps) are assigned to the client at delivery, subject to payment in full.

FPWS retains the right to use anonymized methodology, redacted artifacts, and high-level outcomes in case studies, conference talks, and internal training, unless explicitly limited by the Statement of Work.

Components of FPWS's internal toolkit (the design system primitives, component library, build playbooks, and analysis frameworks) are pre-existing FPWS intellectual property and are licensed to clients for the duration of their engagement.

07

Warranty and disclaimer

Content on this site is provided as our best honest read on the practice we operate. We make no warranty that any specific tactic described will produce a specific result for your business. Search, AI, and platform algorithms change constantly.

For client engagements, warranty terms are spelled out in the Statement of Work. Replatform engagements include an explicit ranking-parity guarantee, defined in that document.

08

Liability

Use of fpws.dev and any free resources we publish is at your own risk. Our liability is limited to the amount you have paid us under an active engagement, or zero if no paid engagement exists.

09

Governing law

These terms are governed by the laws of the United States. Disputes that cannot be resolved by direct conversation will be settled in the appropriate courts.

10

Changes

We may update these terms. The effective date at the top reflects the most recent revision. Material changes that affect active clients will be communicated by email. Continued use of the site after a change constitutes acceptance.

Questions about this policy

Email hello@fpws.dev and we will reply within one business day.