Building and operating a portfolio of software products

Hands-on founder work across knowledge tools, education, website creation, and publishing, with maturity stated product by product.

Business context

ProInstincts brings together product building, software operations, and acquisition work alongside Arthur's executive background.

The problem

Allocating engineering attention across products at different stages, without confusing development activity with customer-ready capability.

Constraints

Finite time, differing product maturity, and product-specific operational requirements. Availability does not demonstrate adoption or revenue.

Arthur’s role

Executive Director of ProInstincts Enterprises, Inc., with hands-on architecture, product direction, and delivery responsibilities.

Diagnosis & decision

Illustrative reasoning: shared engineering practices can help a portfolio, but each product still needs its own readiness evidence.

Architecture & operating approach

Product-specific architecture, delivery, and operational work across Phasoric, ClassLattice, SiteKick, and HeadlineChaos.

Outcome

The portfolio includes publicly available products and work still in development. SiteKick CMS is available; Studio is coming soon and its interest list does not grant product access. No aggregate traction, revenue, or universal production-readiness claim is made.

Executive lesson

Leadership lesson: current building experience complements executive judgment, but product maturity must be communicated honestly.

Choose a useful next step

Explore the work, try a practical tool, or discuss a challenge with Arthur.

Try the free readiness review · Start a conversation