Product Hunt needed screenshots, copy, timing, and somebody to keep the whole thing moving.
Goodword had already launched on its own site in October. Product Hunt offered a separate public page where people could see the product, read a compact description, and respond during a defined launch day.
The work began with coordination rather than publication. The team needed a product name, a short description, images, a maker profile, and a destination that worked for somebody arriving without previous context.
The page also had to match the current product. Screenshots from an earlier mobile beta would not accurately describe a web experience that had continued to change. The text needed to say what Goodword did at that moment rather than repeat every idea from the company story.
The launch path required a basic test. Open the Product Hunt preview, follow the product link, create or access an account, and confirm that the first page explained the next action.
Planning included the responses around the page too. A Product Hunt visitor might ask a question, leave a comment, or report a problem in public. The team needed somebody watching those channels while engineering remained available for actual defects.
By February 2, Goodword was treating Product Hunt as another way to introduce the product after its direct launch.
The page was not live that day. We were still discussing the launch.
The team was still assembling the material and deciding how the Product Hunt description should lead into the current version of Goodword.