Connect with us

Weather where you are

Choose your location or share it once. We round your coordinates to about 1 km before sending them to our site and MET Norway for your forecast. Your choice stays in this browser tab.

Stay close to Boston

Get new Boston stories and Boston Made company updates, delivered as browser notifications.

Choose Enable notifications, then allow notifications in your browser.

Your browser subscription is stored by Boston Made and delivered through your browser’s push service. You can turn notifications off in your browser’s site settings. Privacy policy

Service

Something Is Brewing at Boston Made

Boston Made, Inc. confirms a new project is in development. The company is keeping the details quiet, but it starts early in the morning and belongs in a mug.

Published

on

Close-up of freshly roasted coffee beans

FOR IMMEDIATE RELEASE
November 20, 2026

Boston Made, Inc. confirmed today that a new project has moved out of the notebook and into development. The company is not ready to say everything about it. It is ready to say this much: it starts early in the morning, it smells wonderful, and it belongs in a mug.

Advertisement

Advertisement

For a company that has spent 2026 building websites, apps and newsrooms, the next step is something you can hold in your hands. Boston Made has always been named for two things, a GoldenDoodle called Boston and the city itself, and both of them know the value of a good morning routine.

What the company will say for now

  • The project has a working name, and the name does not try to be clever.
  • It has an address on the internet: bostonmadecoffee.com. Bookmark it.
  • It is being built the way Boston Made builds everything else: slowly enough to get it right, and with the family of brands around it.
  • It is meant to be shared, at a kitchen table, at a desk, or on the walk with the dog.

Some of the best ideas at Boston Made have started over a cup of coffee. This one is the cup.

What the company is not saying yet

Boston Made is holding back the details that matter most to coffee drinkers: what is in the bag, where it comes from, how it will be sold and when the first order can be placed. Those answers will come in a full announcement, not in a hint.

Until then, readers who want to be first in line can watch the Boston Made newsroom and keep an eye on bostonmadecoffee.com. Boston Made+ members will hear about it before anyone else.

Why now

The holidays are when people slow down, gather, and put the kettle on. It felt like the right week to admit that something is brewing.

Advertisement

About Boston Made, Inc.

Boston Made, Inc. is a Delaware corporation founded in 2019 by Nathanael Strickland, Founder & CEO. It is the company behind the Boston Made family of brands, spanning publishing, pets, web design, software and community projects. Learn more at bostonmade.com.

Media contact: sales@bostonmade.com

This release describes projects that are still in development. Names, features, timing and availability may change, and nothing here is an offer to sell a product or service.

Boston Made Foundation Boston Made family Boston Made Foundation The philanthropic arm of the Boston Made family. Visit site →

Advertisement

Latest stories

View all
Continue Reading

Service

Write a Useful Website Brief for a January Project

Nathan Strickland

Published

on

boston brownstone

A January website project can start more clearly if December’s brief describes the problem before the preferred solution. A request for a modern homepage is difficult to evaluate. A request to help customers distinguish two services and complete the correct inquiry gives the team something concrete to investigate.

Gather a small set of examples from the current site. Record the public pages, the confusing wording and the customer tasks affected. Use approved, anonymized inquiry patterns rather than copying personal messages into the brief. Distinguish an observed problem from a theory about what caused it.

Advertisement

Advertisement

Define what a successful change would let a person do. Include operational limits such as who maintains the content, which systems must remain connected and when reviewers are available. If photography or copy needs to be created, say so. A design brief should not quietly assume that a new image library or complete service description already exists.

End with the decisions the first project meeting needs to make. Those might include scope, priorities, content ownership and how the work will be checked. Keep aspirational references as references, not instructions to copy another company. A clear brief gives specialists room to solve the real problem while making it easier for the business to judge whether the solution is useful.

A practical review

A before-and-after comparison can be valuable when the context is explained. Use comparable views and identify what changed in the content or interaction. Do not crop the earlier version unfairly to make the new one look better. If the project included several phases, state which phase the example shows. A customer’s approval of a screenshot does not automatically cover every commercial detail in the surrounding story, so review both together. Keep the approved case-study text with the project record. When the live site changes later, the historical example can remain useful if its date and scope are clear. The reader should understand a particular piece of work, not be invited to infer a sweeping result from a polished image.

Before you finish

  • Describe the customer problem before specifying a visual treatment.
  • Separate observations from assumptions about their cause.
  • Name content owners and existing-system constraints.
  • List the decisions needed to start the project responsibly.

Quick check

How much did you catch? Tap a question to see the answer.

1. What belongs at the start of a January website brief?

Answer: Describe the customer problem before specifying a visual treatment.

Advertisement
2. How should the brief distinguish evidence from guesses?

Answer: Separate observations from assumptions about their cause.

3. Which people and constraints should the brief identify?

Answer: Name content owners and existing-system constraints.

A Brief Structure That Keeps the Problem in Front

A useful brief can fit on two pages. It does not need polish; it needs clarity. The following headings work for most small-business website projects:

  1. The problem in one paragraph. What customers are struggling to do, and how the business knows.
  2. Examples. A short list of pages, links or screenshots showing the problem, with a sentence on each.
  3. Who is affected. The type of visitor or customer task, described by what they need rather than who they are.
  4. What success would allow. Written as actions: “A visitor can tell which of our two services fits them and reach the right form.”
  5. Constraints. Systems that must stay connected, people who will maintain the content, reviewer availability, any fixed dates.
  6. Existing materials. What copy, images and brand guidance already exist, and what will need to be created.
  7. Open questions. Anything the business has not yet decided.

A worked example

Consider a home-services company whose December brief begins: “We want a fresh, modern homepage.” After rewriting, it begins: “Callers often book our standard inspection when they actually need our repair assessment, and staff spend time rebooking them. We think the two services look too similar on the site.” The examples section then lists the two service pages, the shared form and a few anonymized descriptions of misdirected requests. Success is defined as visitors choosing the right service before they call. The constraint section notes that the booking system cannot be changed this quarter. That brief gives the designer and writer a real problem to solve, and it gives the owner a clear way to judge the result.

Separating Observations From Theories

One of the most valuable habits in a brief is labeling the difference between what someone has seen and what they think it means. Observations are things like “Three people this month asked whether we serve their town, which is listed on the page.” Theories are explanations: “The service area is too far down the page.” Both belong in the brief, but under separate labels. Specialists can then test the theory instead of assuming it, and may find a different cause entirely.

Mistakes That Weaken a January Brief

  • Prescribing the solution. “Add a slider to the homepage” closes off better options before anyone has studied the problem.
  • Copying private messages. Summarize patterns from inquiries rather than pasting customer emails, names or contact details.
  • Hidden content assumptions. If the new pages will need new photographs, service descriptions or pricing explanations, the brief must say who will produce them.
  • Reference sites as specifications. Sharing a site you admire can explain a feeling or a structure, but the brief should say what you like about it rather than asking for a copy.
  • No decision maker. Name the person who can approve scope and settle disagreements.

Questions for the first meeting

  • Which problem matters most if only one can be solved first?
  • What will be measured or checked to show the change helped?
  • Who writes and maintains each piece of content after launch?
  • When are reviewers realistically available in January?
  • What is explicitly out of scope for this project?

Why write it in December?

The weeks before a holiday break are often when the problems are freshest. Staff have just handled a busy season and remember which questions came up again and again. Writing the brief now, even roughly, captures that knowledge before it fades over the break. In January, the brief only needs to be checked and refined rather than reconstructed from memory, and the first project meeting can begin with real examples on the table instead of a blank page.

Fenway Web is coming to iPhone

Client news, portfolio work and the Fenway Journal in one app for iPhone, iPad and Apple Watch.

See Fenway Web

The post Write a Useful Website Brief for a January Project appeared first on Fenway Web.

Boston Made Reader Boston Made family Boston Made Reader Free e-reader app for long reads, wires and books. Visit site →

Advertisement

Continue Reading

Service

Give December Website Changes a Smaller Approval Window

Published

on

markets screen

December can leave a website with fewer available reviewers and more time-sensitive messages. A smaller approval window helps the team finish necessary work without assuming someone will be available to check it later. The point is to reduce uncertainty, not to rush an incomplete change into production.

Make a short list of changes that must happen this month. Separate factual updates and reliability repairs from optional improvements. For each necessary item, name the person who supplies the facts, the person who publishes it and the person who checks the result. One person may hold several roles, but the responsibilities should still be explicit.

Advertisement

Advertisement

Set the review deadline before the publication deadline. Leave room to resolve contradictions in hours, offers or availability. Keep the proposed wording and visual in one place so reviewers do not approve different versions. If a required fact is still missing, explain that limitation and reduce the scope rather than filling the gap with a guess.

After publication, send the owner the actual public page and a short check result. Record any temporary wording that needs to change in January. This makes the approval process a completed loop: verified input, reviewed change, tested page and planned follow-up. A shorter queue can be more useful than a long list of festive improvements nobody has time to verify.

A practical review

A product demonstration and a decorative background loop should not be treated as the same component. A demonstration may justify a deliberate play action, controls and an accompanying explanation. The background loop should not be the only place a visitor learns an essential feature. Check the still fallback with the video fully disabled rather than merely paused. The page’s heading, explanation and action should still make sense. If a still image produces the same understanding, compare its actual visual quality with the video’s first frame. An intentional photograph often offers better composition than a frame chosen only because it happened to start the clip. Make the decision around the communication job instead of assuming movement automatically signals a more premium experience.

Before you finish

  • Separate necessary December updates from optional visual work.
  • Name the fact owner, publisher and final checker.
  • Allow time between approval and publication for factual corrections.
  • Record January follow-up for every temporary December change.

Quick check

How much did you catch? Tap a question to see the answer.

1. Which December changes should be separated from optional design work?

Answer: Separate necessary December updates from optional visual work.

Advertisement
2. Who should be named in the approval process?

Answer: Name the fact owner, publisher and final checker.

3. Why should approval happen before the publication deadline?

Answer: Allow time between approval and publication for factual corrections.

Setting Up the December Change Queue

A smaller approval window works best when the queue is visible to everyone involved and short enough to read in one glance. A simple process might look like this:

  1. List every December change on one page. Holiday hours, closure notices, shipping or booking cutoffs, year-end offers, and any repairs already scheduled.
  2. Sort into three groups. Must publish (factual or time-sensitive), should repair (reliability problems customers will notice) and can wait (everything else, including redesign ideas).
  3. Assign three roles to each must-publish item. The fact supplier, the publisher and the checker. Write the names in the queue.
  4. Set two dates per item. The review deadline and the publish date, with at least one working day between them where possible.
  5. Move “can wait” items to a January list. Taking them out of December’s queue protects the important work from distraction.

A worked example

A small bakery needs to publish holiday order deadlines, collection times and reduced opening hours. The owner supplies the dates, a part-time staff member updates the website and the manager checks the published pages. The review deadline is set for a Tuesday, the publish date for Thursday. On Tuesday, the manager notices that the order deadline on the draft differs from the one on the printed flyer. Because there is a gap before publishing, the owner has time to confirm which date is correct, and both the page and the flyer are corrected before customers see either.

Making Reviews Faster Without Making Them Weaker

  • Keep one source of truth. Put the proposed wording, any image and the target page link in a single document or ticket. Reviewers should never have to compare an email draft with a chat message.
  • Ask specific questions. Instead of “Does this look OK?”, ask “Are these dates correct?” and “Does this match what staff will tell customers on the phone?”
  • Approve in writing. A short “Approved” reply attached to the item is enough, and it removes any later doubt.
  • Batch similar changes. If hours appear on the contact page, the footer and a map listing, review them together so they stay consistent.
  • Schedule the follow-up now. Every temporary December message should have a January removal date before it is published.

Common December Pitfalls

  • Last-minute “small” improvements. A new banner style or homepage rearrangement introduced in the final week before a closure can break something nobody has time to fix.
  • Approvals given from memory. A reviewer who approves without opening the page may miss that the published version differs from the draft.
  • Single points of failure. If only one person can publish and they are away, the queue stops. Confirm a backup before the holidays.
  • Guessing at missing facts. If a delivery partner has not confirmed a cutoff, say that the date will be confirmed, or leave the line out until it is.

Questions to settle this week

  • Which changes genuinely must happen in December?
  • Who is unavailable, and when?
  • Who can publish and check if the usual person is away?
  • What will need to be undone in January, and who owns that task?

What this means for the rest of the month

A shorter, clearer queue usually means fewer changes, and that is the point. Each December update that does go live has confirmed facts behind it, a named reviewer and a planned exit. The improvements that were set aside are not lost; they sit on the January list with notes attached, ready for a time when reviewers have the attention to give them. Customers are better served by a few dependable updates than by many rushed ones that nobody had time to verify.

Fenway Web is coming to iPhone

Client news, portfolio work and the Fenway Journal in one app for iPhone, iPad and Apple Watch.

See Fenway Web

The post Give December Website Changes a Smaller Approval Window appeared first on Fenway Web.

Boston Made Pets Boston Made family Boston Made Pets Pet apparel and gear inspired by Boston the GoldenDoodle. Visit site →

Advertisement

Continue Reading

Service

Boston Made publishes its 2026 ecosystem audit and editorial review

Published

on

business glass

FOR IMMEDIATE RELEASE
November 18, 2026

Boston Made has begun a 2026 ecosystem audit and editorial review across its owned digital properties, with a focus on clarity, continuity, preservation, and a better experience for visitors moving between the family of brands.

Advertisement

Advertisement

The review brings the network’s public-facing roots into one operating picture: the company newsroom, foundation and community properties, brand and product sites, and the focused digital experiences built around Paxton, Pupwear, Grand Strand, SpotCheck, Bosstox, Lumo, and other Boston Made initiatives.

The work is intentionally practical. Existing homepages and backups are being preserved, aliases and redirects are being identified, static applications are being kept separate from publishing sites, and customer properties are being treated as a protected class rather than folded into the Boston Made editorial stream.

The result is a cleaner foundation for the next stage of the ecosystem: better navigation between related properties, clearer ownership boundaries, stronger editorial consistency, and a newsroom that can document meaningful work without manufacturing urgency or confusing an internal review with a service outage.

“The strongest ecosystem experience is the one that feels connected without feeling crowded,” said Boston Made in its 2026 editorial review. “Every property should have a clear reason to exist, a clear path for visitors, and a record that can be trusted.”

During the remainder of 2026, Boston Made will continue refining its editorial calendar, documenting retrospective material clearly when it is needed for archival continuity, and publishing new announcements only when there is a real update worth sharing.

Advertisement

For additional information, visit the Boston Made newsroom at bostonmadeinc.com.

Publishing note: This release is for Boston Made-owned editorial properties only. Customer websites, redirects, staging hosts, and static app endpoints are excluded. Any historical catch-up material must be labeled Retrospective and must not imply that a new event occurred on the backdated date.

Beacon Federal Partners Affiliate Beacon Federal Partners Independent government-contracting firm and Boston Made affiliate. Visit site →

Advertisement

Continue Reading
Advertisement

Advertisement

Ad

Advertisement

Trending

--:--·---·--°