I build small software around work people already do.
I’m Anthony Jones, an independent product engineer in Rome, New York. ANTHONY.online is where the focused apps live—and where I document how they are built.
Why a separate app division
A calculator, audit utility, or embeddable component has a different job from an agency service page or a CRM product. Giving those tools their own home keeps the product story clear and lets the technical documentation go as deep as it needs to go.
The rule is simple: one repeated task, a visible method, a result you can use, and a scope small enough to maintain properly.
How the three domains divide the work
- designedbyanthony.online
- Apps, calculators, embeddable widgets, and technical build notes.
- designedbyanthony.com
- Custom websites and Local Visibility for service businesses.
- vertaflow.io
- CRM, pipelines, client operations, and growth tooling.
They share a builder and technical standards, but each domain owns a distinct topic and customer job. Unique pages self-canonicalize; retired overlaps redirect to the domain that actually owns the subject.
What I optimize for
- Understandable systems. The method should be visible in the interface and documentation.
- Static-first delivery. A page should not need a server merely because a framework can provide one.
- Accessible interaction. Keyboard, focus, contrast, labels, and reduced motion are product requirements.
- Honest boundaries. A planning estimate is labeled as one; an integration states what it sends and where.
- Reproducible proof. Tests, release identity, and dated measurements matter more than permanent score claims.