An education program
For an online education company, we developed an expert training program with a structured learning path, career-oriented material and capstone work. The job was to make the program coherent from its foundations through practical application.
The source work included foundations, career tracks, capstone projects and a design for a pilot cohort. These parts serve different jobs: introducing the material, making it relevant to a learner’s direction, and giving the learner a way to apply it. The engagement brought them into one program rather than leaving them as unrelated lessons.
A publishing foundation for an advisory practice
For an independent financial advisory practice, the scope included custom page templates, a blog system, an editorial calendar and a local search page. These pieces gave the practice a repeatable way to publish.
Page templates made the structure reusable; the blog organized the articles; the editorial calendar provided a plan for what to publish next. The local search page addressed the practice’s geographic audience. Together these were a foundation for continued publishing, with the practice responsible for its professional advice.
A consulting firm’s site and standards
The consulting engagement included homepage development, site copy, wireframes and secondary pages. We also left development standards and an element registry so future changes could follow the same design decisions.
A production-readiness review and service-package work were part of the engagement.
The standards and element registry were handover material as well as design work. They gave a future contributor a reference for the components already in use, reducing the need to rediscover decisions when changing the site. Service-package work helped connect the pages to a clear description of the firm’s offer.
Registration and a foundation website
For a youth sports nonprofit, we built website and registration-related work, including submission alerts and a registration handoff.
For a family foundation, the delivered scope was a website. A separate portal was planned; it is not described as delivered.
The sports registration handoff connected a submitted form to an action the staff could take, with alerts drawing attention to incoming work. The foundation engagement had a different boundary: its public website and domain formed the delivered front door, while the separate portal remained future work.
Small scope still needs a clear finish
The common thread is a defined job and an explicit boundary. A website, a training program and a future portal are different deliverables, and the record should keep them separate.
Questions & answers
A few useful distinctions
What was in the education program?
A structured path with foundations, career-oriented material, capstone work and a design for a pilot cohort.
What did the advisory practice receive?
Custom page templates, a blog system, an editorial calendar and a local search page—a foundation for a repeatable publishing process.
What supported future changes to the consulting site?
Development standards and an element registry accompanied the copy, wireframes and pages. These documented the design decisions for later contributors.
What did the sports nonprofit’s registration work do?
It connected website registration to submission alerts and a handoff the staff could act on.
Was the foundation portal delivered?
No. The foundation website was delivered; the portal is planned. They are separate scopes of work.
Public sources
These links provide the public material and background identified below. Client engagements are described by type.
- How we work
Background on the Zen Aegis method; not an independent audit of a private engagement.