Migrations
Headless & composable
Design & growth
Marketing shipping pricing changes, integration pages and comparisons without filing a ticket, on a site your engineers do not have to maintain. We will tell you which pages are worth building before we build any of them.
Trusted by
Pricing changes and the page cannot hold the new tier structure. Sales asks for a comparison page against the competitor everyone keeps mentioning. Someone wants an integrations directory, and the honest answer is that each one would be a hand-built page. So the site stops being something marketing runs and becomes something marketing requests.
None of that is a design problem. The site looked fine on launch day. It was built as a brochure for a product that was going to keep changing.
We build the page types before you need them, because retrofitting a CMS around a page you already published is the expensive version.
Content models built for the page types a SaaS site accumulates, so a new integration page or a new tier is a CMS entry rather than a build ticket.
Demo requests, trial signups and gated content routed into the CRM with the fields mapped, so marketing can prove what the site returned rather than guess at it.
The pages that are hardest to change later: pricing tiers, feature comparison, changelog and documentation, structured so they survive the next pricing change.
Schema, semantic markup and crawlable structure built in, so the pages you publish can be found and cited rather than only linked from the nav.
Built for teams where marketing owns the site, the page count grows every quarter, and someone would notice within the day if organic signups dropped.
The same brief, built two ways.
We build software on these platforms, not only with them. Two of our own products run on the Webflow Marketplace, ConsentBit for cookie consent and AccessBit for accessibility, which is how we know where the platform stops.
Page type inventory, CMS model, what we recommend not building
Figma tokens, component library, landing page system
Semantic build, CRM routing, schema, programmatic page setup
Crawl comparison, Core Web Vitals, CMS training, recorded walkthrough
Phase 01 usually ends with a shorter list than you arrived with, because the pages nobody will maintain are the ones that age worst.
Bring us the pages you cannot ship and the ones you keep rebuilding. A technical lead will tell you what to model, what to automate, and what is not worth having.
This is the part nobody scopes, and it is where SaaS sites age badly.
The hardest page to change later. Tiers get added, features move between them, and annual billing arrives. Built as a structure rather than a layout, a pricing change is an afternoon. Built as a design, it is a redesign.
One page per tool you connect to, and each one can rank. Built by hand, nobody ever makes the fortieth. Built from a collection, the fortieth costs the same as the fourth.
The pages buyers search for by name when they are close to deciding. They need to be honest to work, and they need a structure so the twelfth one is not a fresh build.
Usually owned by product, usually on a different subdomain, and usually invisible to search. Worth deciding deliberately rather than by default.
We model the page types in phase 01, before design, because the cost of a page type is almost entirely in whether it was planned for.
The page types we inventory before designing a SaaS site, what each one costs to maintain, and which ones are usually not worth building.
The page types, nothing else.
“We originally hired Seattle New Media to build a complex, layered resource page to assist our users and intuitively drive them to additional content...”
“We needed our webflow website built in a really short timeline and Seattle New Media was able to work within not only our time constraints but...”
“Partnered with Seattle New Media on a project and they were awesome. Super collaborative, tons of experience, just overall a great...”
“Seattle New Media has helped us revamp our website and increase online traffic with Sharpspring CRM, Social Media Marketing, Search Engine...”
Usually Webflow, because marketing teams can ship from it without a developer and it handles the page volume a SaaS site accumulates. Where a headless setup fits better we will say so, and we build those too.
Four to eight weeks for a standard build. Eight to twelve where there is heavy content migration, a docs structure or integrations in scope.
Most engagements run $8,000 to $30,000+, depending on page count, how many page types are in scope and what has to be integrated. Fixed scope and fixed price after a discovery call.
No. We build the marketing site, the pricing, the docs structure and the conversion paths. Product UI is a different discipline and we would rather tell you that than take the work.
Yes, and that is usually the point. Built from a collection rather than by hand, the fortieth page costs the same as the fourth.
Yes, if the pricing page is built as a structure. That is a phase 01 decision, which is why it is the first thing we model.
Both. The difference shows up in the conversion paths, trial signup versus demo request, and in how much the site has to explain before a human is involved.
Yes. We crawl before design starts, map every URL, test redirects on staging and compare crawls before go-live. Website redesign →
Yes. Form routing into HubSpot or Salesforce with fields mapped and tested, plus GA4 and consent mode. Webflow integrations →
30 days of ranking and 404 monitoring, CMS training, and a recorded walkthrough you keep. Most clients stay on retainer.
Bring us the pricing change that needs a developer, the comparison page sales keeps asking for, or the site you inherited. A technical lead will come back with what to model and what to leave alone.
Reviewed by an engineer, not a salesperson.
