Website Design / Developer Tools
Developer Tools Website Design
Developer tools website design is the design of the marketing website for an API, SDK, infrastructure product or developer platform: the pages that let a developer judge the tool from real code and let an engineering lead approve it from pricing, security and maintenance evidence. Gestures designs developer tools websites with the documentation treated as part of the site, not as a separate destination.
A developer tools website costs $3,500 with Gestures as a Framer or Webflow project covering design, build and launch, with an average delivery of 2–4 weeks. Design-only work runs on the $2,250 weekly sprint or the $7,500 monthly partnership.
Readers
One website, four readers with different questions
A developer tools website serves four readers: the developer who tries the tool, the engineering lead who approves it, the security reviewer who checks it and the finance owner who pays for it. Each reader needs a different page and accepts a different kind of evidence, so we map the readers before we draw the sitemap.
| Reader | Their question | Page that answers it | Evidence they accept |
|---|---|---|---|
| Developer evaluating the tool | Their questionCan I get this working today? | Page that answers itHomepage and quickstart | Evidence they acceptRunnable code, a free tier and a test key without a sales call |
| Engineering lead | Their questionWill this hold up in production? | Page that answers itProduct, integrations and changelog | Evidence they acceptSDK versions, uptime history, dated releases and migration guides |
| Security reviewer | Their questionWhat happens to our data? | Page that answers itSecurity and compliance | Evidence they acceptReports to request, data residency, SSO and audit logs |
| Finance owner | Their questionWhat will this cost at our volume? | Page that answers itPricing | Evidence they acceptA worked monthly example and the price after the free allowance |
Website and docs
Where the marketing site ends and the docs begin
Documentation is the resource developers learn from most, so a developer tools website treats the docs as its most important page and designs the crossing between the two. In the 2026 Stack Overflow Developer Survey, 58.9% of 14,530 respondents had learned to code in the past year through technical documentation, ahead of AI code generation tools at 52.6%.
We design that crossing with one shared header and one search across marketing pages and docs, a Docs link in the primary navigation and a link from every marketing claim to the exact documentation page behind it, never to the docs home.
| Marketing page | Links to | Why the link matters |
|---|---|---|
| Homepage code sample | Links toThe quickstart step that sample comes from | Why the link mattersThe developer continues from the same line of code |
| Pricing limits | Links toThe rate limit and quota reference | Why the link mattersEngineers check limits against their own traffic |
| Integrations page | Links toEach SDK or integration guide with its version | Why the link mattersThe version decides whether it fits their stack |
| Security page | Links toAuthentication, SSO and data handling docs | Why the link mattersReviewers need the technical detail behind the claim |
| Changelog | Links toMigration guides for breaking changes | Why the link mattersA release note without a migration path stops an upgrade |
Code on the page
Code samples on a marketing page follow the docs' rules
A code sample on a developer tools website has to be as accurate as the documentation, because developers hold vendor documentation to a high standard. In the same 2026 survey, 68.4% of 14,049 respondents called accuracy very important for product, vendor or API documentation.
- Real and runnable: the sample calls a current endpoint and works as shown, with values to replace, such as YOUR_API_KEY, clearly marked.
- Text, never an image: the code is selectable, has a copy button and reads correctly to screen readers and search engines.
- One source: your engineers keep the sample in a tested file, and the website renders that file, so a breaking change updates the site and the docs together.
- Language tabs that remember the visitor's choice across every page.
- Syntax colors that meet contrast requirements in both light and dark themes.
Usage pricing
A usage-based pricing page with a worked month
A usage-based pricing page works when it shows one complete month at a realistic volume, because developers estimate cost from their own traffic rather than from a unit price. We design the page around four facts per unit: what is measured, the free allowance, the price after it and an example month.
| Unit | Free each month | Price after the free allowance | Example month |
|---|---|---|---|
| API requests | Free each month100,000 | Price after the free allowance$0.50 per 10,000 requests | Example month600,000 requests cost $25 |
| Storage | Free each month5 GB | Price after the free allowance$0.10 per GB | Example month45 GB costs $4 |
| Team seats | Free each month3 | Price after the free allowance$10 per seat | Example month8 seats cost $50 |
In this illustrative example the month totals $79 for 600,000 requests, 45 GB and 8 seats. Your team supplies the real units and prices. Our guide to pricing page design covers plan limits and billing context in more depth.
Proof
Proof that an engineering lead can check
An engineering lead approving a developer tool looks for evidence that the tool is maintained and will stay maintained, so the website puts dated, checkable signals where that lead looks for them: on the product, integrations and security pages, not only in the footer.
- A changelog with dates and version numbers, linked from the main navigation.
- A public status page with incident history.
- Each SDK with its current version and the date of its last release.
- The repository link for every open-source component, with its license.
- Customer logos and case studies only with the customer's written permission and the customer's own numbers.
Gestures does not invent proof. Every logo, number and quote on a developer tools website comes from your team, with the customer's permission.
Our own setup page
The setup page we designed for our own MCP server
Gestures runs a public MCP server that ChatGPT, Claude and other compatible AI apps can connect to, and its setup page applies the rules on this page to a developer integration of our own. The page opens with the one value a developer needs, the server URL, ready to copy. Authentication, transport and key requirements follow as a single line of facts, and setup instructions are split by AI app instead of merged into one generic list.

Scope and cost
Developer tools website scope and cost with Gestures
A developer tools website costs $3,500 with Gestures as a Framer or Webflow project covering design, build and launch, with an average delivery of 2–4 weeks. Design-only work runs on the studio plans: $2,250 per week, $4,000 for a two-week sprint or $7,500 per month for ongoing work across releases.
| Scope | Typical pages | Plan |
|---|---|---|
| Launch site for a new API or SDK | Typical pagesHomepage with code, pricing, security, changelog and the docs entry | PlanFramer or Webflow project, $3,500 |
| Homepage and pricing rework | Typical pagesFirst screen, code sample and usage pricing with a worked month | PlanTwo-week sprint, $4,000 |
| Docs entry and navigation | Typical pagesShared header, search entry, handoff links and the docs home | PlanWeekly sprint, $2,250 per week |
| Ongoing releases | Typical pagesLaunch pages, changelog design, new SDK and integration pages | PlanMonthly partnership, $7,500 per month |
The screens developers use after sign-up, such as API keys, logs, webhooks and usage, are covered on our developer tools product and website design page. For AI products sold beyond developers, see AI website design.
Monthly partnership
$7,500$10,500USD / month
Studio $7,500 + Growth $3,000 / month
For a developer tools website that changes with each SDK, integration and API release. Set the current focus each month and review what needs attention next.
Strategy · Design · Review
Work starts within 1 day of payment.
Cancel anytime.
Start your projectWeekly sprint
$2,250$4,000USD / week / 2 weeks
+ $3,000 / month for Growth
For one part of the site, such as the homepage and its code sample, the usage pricing page or the docs entry. Agree the pages and the engineers who review technical content before starting.
Save $500 with two weeks: $4,000 instead of $4,500.
Strategy · Design · Review
Work starts within 1 day of payment.
Cancel anytime.
Start your projectAdd Growth to a studio plan
SEO, content strategy and content production, alongside your design team. Growth is billed monthly. Cancel anytime.
+$3,000 / month
Compare all plans, see the Framer website project or book a call to agree the first pages.
Questions
Questions about developer tools websites
Should the docs live on the same domain as the marketing site?
Docs work best on the same domain, such as example.com/docs, because they share one navigation, one search and one sign-in state with the marketing site. A separate docs platform still works when it uses the same header and links back to the exact marketing page.
Should a developer tools homepage show code?
Yes. A developer tools homepage shows a short, real code sample in its first screen, in the language most of your users write, with tabs for the others. The sample is the first step of the quickstart, so copying it starts the integration.
Do developer tools websites need a dark theme?
A developer tools website needs a dark theme when its docs, console or editor integrations have one, so the visitor does not switch brightness between them. Follow the system setting through prefers-color-scheme and offer a manual switch.
How do you keep code samples on the website accurate?
Code samples stay accurate when the website renders them from the same tested files as the docs. Your engineers own the files; Gestures designs the code block, its tabs and its copy behavior.
Can one website present an open-source project and a paid product?
Yes. One website presents both when the navigation separates them by task: the open-source project gets its repository, license and community links, and the paid product gets pricing, support and security pages. Each page states which edition it describes.
Can our team update the website after launch?
Yes. In a Framer or Webflow build, the changelog, integrations and blog become CMS collections your team edits without design work, while the layouts stay consistent.
How much does a developer tools website cost?
A developer tools website costs $3,500 with Gestures as a Framer or Webflow project with design, build and launch, delivered in 2–4 weeks on average. Design-only work costs $2,250 per week or $7,500 per month. See pricing for every plan.
A conversation
Send us your homepage and your quickstart
Send the link to your website and the quickstart it points to, and tell us which reader the site serves worst today. We can agree the first pages and whether Gestures is the right fit. For the wider service, see website design.