A small, hands-on team
CustomNameTrace is built and maintained by a small team rather than a large company, and we'd rather be upfront about what that means than pad this page with invented job titles and stock-photo headshots. There's no marketing department here, no growth team optimizing sign-up funnels — there's a small group of people who care about the specific, unglamorous problem of making a tracing worksheet render correctly, and who do the actual engineering and writing themselves. If you've used the site, you've used something one of us built directly, not something assembled by a large anonymous org.
We're not going to publish individual names and photos on this page. That's a deliberate choice, not an oversight: a lot of small sites pad out a "team" page with fabricated bios and generic headshots purely to look bigger than they are, and we think that's a worse trust signal than just being honest about being small. If you want to reach an actual person rather than read about a hypothetical team, the Contact page goes to a real inbox that a real person reads.
What we actually spend our time on
Most of the engineering effort behind this site is invisible if it's working correctly, which is exactly the point. Getting a custom handwriting font's guide lines to align identically in a browser preview and a server-rendered PDF — two completely different rendering engines with different font metric handling — took far more iteration than anything user-facing on this site. So did making sure the page-width math holds up when someone adds a decorative border, or that a worksheet with three fields (like Family & Safety Info) doesn't assume every family looks the same. None of that shows up as a feature you'd list in a press release. It shows up as a worksheet that just works when you print it.
The other half of the work is editorial, not engineering: writing a genuinely different article for each worksheet type instead of running the same template with the keyword swapped. That's slower, and it's also the actual point of the site's structure — see our About page for more on why we built it that way instead of the faster version.
How we make decisions
We don't run this by committee, and we don't run it by pure metrics either. When something in the product isn't right — a guide line sitting a few pixels off, a form field that assumes a two-parent household, a placeholder that reads like corporate copy instead of a real example — the fix happens because someone noticed it and thought it mattered, not because a dashboard flagged it. That's slower than an A/B-tested, growth-hacked product loop, and we think it produces a better tool.
Working in the open, mostly
We'd rather ship a smaller number of worksheet types that are each genuinely well-built than a large catalog of near-duplicates. If you've read our About page, you've seen the reasoning: search engines and real users both notice the difference between a page with something to say and a page that exists purely to rank for a phrase. We apply the same discipline to our own roadmap — a new worksheet type goes live when its rendering is correct and its article is real, not on a launch-date deadline.
Get in touch
If you're a teacher, occupational therapist, or parent with a specific worksheet type you wish existed, or you've found something that doesn't look right on a page, we want to hear about it directly — not through a support ticket queue. The Contact page is the fastest way to reach us, and the FAQ covers the questions we hear most often about how the tool works and what we do (and don't) collect.
