JASPER × frnk. | Parent portal
The parent portal

Your knowledge.
A clearer way to access it.

A branded resource experience that makes JASPER's information organized, accessible, and easier for parents to use, with a phased approach to building and expanding it.

What we heard

The immediate priority is to make your existing information clear, organized, and accessible to parents through a branded portal.

Your materials already have a distinctive visual identity. We would preserve that personality while shaping the content, navigation, and functionality around your preferred parent experience.

Two build approaches

Our recommended direction

Customize and leverage existing software and tools

Customize existing software and tools to JASPER's design, experience, and functionality preferences, creating a portal shaped around your vision.

Following our initial review of the conversation and materials, the capabilities discussed so far appear to be largely standard: organized resources, parent access, mobile accessibility, and content-based assistance. Our recommendation is to leverage existing software for those foundations and customize the experience around them.

This approach is intended to reduce development time and cost compared with recreating the underlying software from scratch, while reserving custom development for requirements that need it.

The blueprint phase will confirm fit, constraints, ongoing costs, and the implementation scope before we commit to the build.

Also available

Build the software from the ground up

Develop the underlying backend software, access systems, content-management functionality, and application logic specifically for JASPER rather than relying on existing software for those foundations.

We are happy to pursue this direction if you prefer it or if the requirements call for that level of control.

Both approaches include a JASPER-specific design and user experience. The distinction is how much of the underlying software we build ourselves.

We would separately scope development, infrastructure, testing, and maintenance so the full commitment is clear.

A four-phase approach

Each phase would have its own scope, roadmap, deliverables, and approval point. We recommend defining the next phase while completing the current one, so decisions reflect what we learn rather than assumptions made at the outset.

PHASE 01

Blueprint & alignment

Calibrate the vision and establish the decisions needed to build confidently.

  • Confirm parent audiences, priorities, and key user journeys.
  • Inventory launch materials and map the resource structure.
  • Establish visual direction through representative screens and the sample demo.
  • Define functionality, parent access, mobile expectations, and administration.
  • Review content permissions, privacy needs, and ownership responsibilities.
  • Compare the two build approaches and agree on the implementation direction.
Output: An agreed blueprint and a scoped Phase 2 roadmap, budget, and timeline.
PHASE 02

Build the resource hub

Turn the approved blueprint into the initial parent-facing portal.

  • Build the branded home screen, topic navigation, and resource layouts.
  • Organize and publish the approved launch content.
  • Implement parent login and agreed access permissions.
  • Configure the agreed mobile experience.
  • Set up content updates and parent-access administration.
  • Test, review, and prepare the portal for launch.
Output: A launch-ready resource hub and administration handover, subject to the agreed acceptance criteria.
PHASE 03

AI & interactive experiences

Add support and interaction around the resources parents are using.

  • Prepare approved content for the AI resource assistant.
  • Define answer boundaries, resource links, and human escalation.
  • Test and review assistant responses with JASPER's content owners.
  • Prioritize more customized user experiences, such as digital worksheets, guided examples, or planning tools.
  • Validate these additions with representative users before wider release.

The assistant can initially focus only on approved portal content. Preparing the broader SOP and knowledge library is not a prerequisite for that focused scope. Its proposed role is resource guidance, not diagnosis or individualized intervention advice.

Output: An approved resource assistant and the interactive enhancements selected during Phase 2.
PHASE 04

Ongoing expansion

Scope the next priorities during Phase 3, based on feedback, usage, and JASPER's evolving goals.

  • Consider additional approved resources and broader knowledge organization.
  • Identify useful enhancements to navigation, personalization, or interaction.
  • Assess any additional access or facilitator workflows.
  • Agree on ongoing content maintenance, assistant review, and product support.
Output: A separately agreed roadmap for the next stage, not a predetermined list of features.
Visual sample

A glimpse of the experience

Open the demo video in a new tab ↗

Any assistant interaction in the sample illustrates a potential later-phase experience; it does not imply production AI is included in the initial resource-hub build.