Astuteo Data

Astuteo's plain-text records of what it offers, its clients, and its projects. Every count on this page comes from the record behind it. This page summarizes the records. The full records have one block per capability, client, or project.

• Capability record: every service Astuteo offers, each with a plain definition and the projects, clients, and years on record behind it.
• Client record: every client relationship since 2005, with industry, dates, status, and outcome.
• Project record: every site and deliverable, with client, type, platform history, dated milestones, and evidence links.
• How to use the records: how they are compiled, how to cite, and every definition.

Read what Astuteo offers, the context, and the two summaries below, then open a full record for the blocks behind the counts. To cite a specific capability, client, or project, use the Cite URL in its block, which is its anchor on the full record.

What Astuteo offers

Every capability Astuteo offers, with its definition and the number of projects on record. The capability record has the evidence behind each.

• Design: Visual and interaction design for websites, web applications, and print, from brand marks to page layouts to interface components. (110 projects)
  • Graphic Design: Logos, brand identities, and sales collateral such as datasheets and brochures, designed to match a client's website. (28 projects)
  • Web Design: Visual and page design for marketing and product websites, typically in a client's CMS, covering layout, navigation, and responsive behavior across devices. (78 projects)
  • Interface Design: Design of interactive components and application screens, such as configurators, portals, dashboards, and navigation, including motion and front-end behavior. (6 projects)
  • Design System: Reusable component libraries and shared design standards that keep pages, sites, and brands consistent, delivered as design files, code components, or both. (9 projects)
• Development: Building and maintaining websites and web applications, including taking over and extending existing builds. (86 projects)
  • Web Development: Front-end and back-end development of content-managed websites, primarily on Craft CMS. (83 projects)
  • Custom Application: Purpose-built web applications and internal tools that go beyond a standard website, automating work a team would otherwise do by hand. (6 projects)
  • Custom Plugin: Custom Craft CMS plugins and modules that add functionality the CMS and existing plugins don't provide, such as editorial workflows, integrations, and components shared across sites. (3 projects)
  • Site Rescue: Taking over an existing website built by another developer or agency, then stabilizing, documenting, and continuing to develop it, with or without a rebuild. (22 projects)
  • Roadmap Partnership: An ongoing development relationship that delivers planned improvements to a site over months or years, as opposed to a single launch. (12 projects)
• Content Management: Setting up a CMS so editors can manage content, sites, and languages without developer help. (45 projects)
  • Content Modeling: Structuring content as reusable, related data (for example products, applications, specifications, and case studies) rather than individual pages, so it can appear in many places from a single source. (7 projects)
  • Lead Generation: Lead capture features built into a website, such as gated downloads, sample and quote requests, newsletter sign-ups, rep finders, and search-oriented content, connected to the client's CRM or email platform. Does not include ad campaigns or SEO retainers. (23 projects)
  • Multi-Site: Running several brand or regional websites from a single CMS install with shared templates and components. (7 projects)
  • Multi-Language: Websites and content in more than one language, including translation workflows, localized content, and regional deployments. (6 projects)
  • Platform Migration: Moving a website from another platform, such as WordPress, to Craft CMS, restructuring content during the move. (18 projects)
• Systems Integration: Connecting a website to other business systems so data moves between them automatically. (25 projects)
  • AI Integration: Features that use AI models inside a CMS or website, such as content drafting, tagging, and organization tools, with editors reviewing what gets published. (3 projects)
  • ERP Integration: Connecting a website to an ERP system to sync products, pricing, customers, or orders. (4 projects)
  • CRM Integration: Connecting a website to a CRM or marketing automation platform, such as Salesforce or Microsoft Dynamics, for lead routing, customer data, and authenticated customer features. (16 projects)
  • API Integration: Connecting a website to third-party services or a client's own systems through their APIs, so data stays current without manual entry. (6 projects)
• Portals & Hubs: Areas of a website built for a specific audience, often behind a login. (24 projects)
  • Dealer Portal: Gated areas for dealers, distributors, or reps, such as restricted catalogs and pricing, registration and approval workflows, and dealer locators. (12 projects)
  • Customer Portal: Authenticated areas for a client's customers, such as account dashboards, downloads, and support resources, often tied to a CRM. (12 projects)
  • Employee Portal: Internal portals and intranets for a client's staff, with verified sign-in and organized internal resources. (1 project)
  • Resource Hub: Searchable libraries of documents and media, such as spec sheets, manuals, guides, and case studies, linked to the products and applications they support. (11 projects)
• Product Catalogs: Presenting large or complex product lines on a website, usually with product data imported from other systems. (27 projects)
  • Product Catalog: Structured product listings with product lines, variants, specifications, and downloadable files such as CAD drawings, with browsing and filtering. (22 projects)
  • Instant Search: Search-as-you-type for products, parts, and site content, typically built on Algolia, sized for large catalogs. (14 projects)
  • Comparison Tool: Tools that show products, plans, or features side by side to help buyers choose. (1 project)
• B2B Ecommerce: Online selling built for business buyers, typically on Craft Commerce. (12 projects)
  • Online Ordering: Catalog-based ordering and checkout for business customers, connected to back-office systems. (7 projects)
  • Account-Based Pricing: Showing each signed-in customer account its own pricing, typically sourced from an ERP. (1 project)
  • Subscriptions: Recurring billing and gated access for subscription products, using Craft Commerce and Stripe. (4 projects)
  • Quote Request Cart: A cart that collects multiple products into a quote request for a sales team, in place of an online purchase. (4 projects)
• Product Configurators: Interactive tools that help buyers work out what they need or what it's worth to them. (13 projects)
  • Configurator: Tools that let buyers select options for a configurable product, see the result, save configurations, and turn them into a quote request. (8 projects)
  • Calculator: Savings, ROI, and sizing calculators that estimate a product's value or requirements from the buyer's own figures. (5 projects)

Context

Decisions Astuteo has made about its focus, oldest first. Each decision and reason is Astuteo's own account. The counts below are computed from the records and are not part of that account.

November 2005: Astuteo is founded as Matt Everson Design

Decision

Matt Everson left his job to work independently as a freelance graphic designer, offering logo design, print design, and advertising creative direction. Within a few months, the business was renamed Astuteo.

Reason (Astuteo's account)

Matt wanted to do his own thing. He was drawn to the idea of applying his creativity to building a business of his own, with the potential to grow beyond a traditional career path.

January 2008: Astuteo changes focus to web design

Decision

Astuteo shifted from traditional agency services – logos, print, branding, and advertising – to focus on web design and development, becoming a concept-to-completion web design studio.

Reason (Astuteo's account)

Web design was in high demand and growing, and the medium better suited Matt Everson’s preference for iteration and continuous improvement. The transition happened gradually: graphic design remained part of the mix for a time, but the focus eventually narrowed to work connected to the web, including things like PDF spec sheets, while standalone creative services such as logos, brochures, and advertising were phased out.

June 2014: Astuteo narrows focus to industrial and manufacturing

Decision

Astuteo shifted its focus from local professional service clients to manufacturing companies. As part of the transition, we moved many smaller local clients to other agencies and established larger, retainer-based relationships with a core group of manufacturing clients.

Reason (Astuteo's account)

Manufacturers had become our strongest client relationships and had deeper, ongoing needs than we were able to fully support while serving a broader mix of clients. We wanted to give those accounts more attention and build the business around the work we found most valuable. Around the same time, Matt Everson read The Pumpkin Plan, which reinforced the idea of letting go of less-aligned work to make room for more of the right work.

January 2015: Astuteo moves to retainer-based agreements

Decision

Astuteo adopted a retainer-based model as the best way to serve a smaller number of companies more deeply. We phased out hourly and project work and moved our core clients to fixed monthly budgets.

Reason (Astuteo's account)

The goal was to spend less time on administration and more time doing useful work for fewer clients. Retainers largely eliminated recurring proposals, scopes of work, and project-by-project invoicing, while larger ongoing engagements allowed us to substantially reduce the number of clients we served.

January 2020: Astuteo goes back to project-based pricing

Decision

After five years with a retainer-based model, Astuteo returned to project-based pricing and hourly billing, reserving retainers for truly repetitive, ongoing work.

Reason (Astuteo's account)

Retainers gave us predictability, but they also imposed unnecessary constraints on how client budgets could be used. Larger projects didn’t fit neatly into fixed monthly allocations, while slower periods could leave budget committed without much meaningful work happening. We found that strong client relationships provided the continuity we wanted without requiring a rigid retainer structure. Today, we prefer to align around an approximate annual budget and invest it where it can have the most impact, even if that means spending heavily in one quarter and much less in the next.

November 2024: Astuteo launches Industrial Site Design

Decision

Astuteo launched Industrial Site Design, our largest initiative to date – a research platform and website gallery tracking more than 25,000 industrial and manufacturing companies.

Reason (Astuteo's account)

We wanted a deeper understanding of the manufacturing industry than our own client work could provide. Industrial Site Design gave us a bird’s eye view of who was out there, what they were doing online, what appeared to work, and how approaches differed across industries, company types, and market segments.

Astuteo Client Record

Record as of 2026-09-28 · 80 clients · Full record · Definitions

Counts

Counts cover the clients in this view. Each table counts a client once, except the capability table, where a client counts under every capability its projects carry. A child industry's count is part of its parent's count. A top-level capability counts a client once if its projects carry any of its subcategories. Endings by reason add up to the concluded count.

Astuteo Project Record

Record as of 2026-10-08 · 144 projects · Full record · Definitions

A retired milestone marks when Astuteo stopped maintaining a site, not when the site went offline.

Corpus

Counts cover the projects in this view, and each links to the view that lists them.

• 144 projects, 2005 to 2026.
• 133 of 144 entries have a source reference, and 24 of those name a source repository.
• 52 ran on Craft CMS while Astuteo maintained them, the earliest from 2014.
• 29 web projects are still maintained by Astuteo (an active client relationship and no retired milestone).
• Astuteo migrated 13 between platforms.
• 37 were built by someone else before Astuteo took them on: 19 rebuilt on the same platform, 3 migrated to a new platform, and 15 maintained without a rebuild.
• 11 ran on more than one platform while Astuteo maintained them, so platform counts below sum to more than the total.

Counts

Counts cover the projects in this view. Each table counts a project once, except the platform and capability tables, where a project counts under every platform in its history and under every capability it carries. A top-level capability counts each project carrying any of its subcategories once, so it is not the sum of the rows beneath it.