Skip to content

🚀 Quick Start Guide

Welcome to GetCimple's internal documentation! This guide helps internal team members quickly orient themselves based on their role in building and launching the platform.

Choose Your Path

👨‍💼 I'm a Business Partner

Goal: Understand market opportunity, business strategy, and competitive positioning

Quick Path:

  1. Start with Project Overview to understand what we're building
  2. Review Core Principles to understand our strategic approach
  3. Study Value Proposition and Market Analysis

Key Documents:

👨‍💻 I'm a Developer/Technical Team Member

Goal: Understand technical architecture and start contributing to development

Quick Path:

  1. Review Technology Stack Overview to understand our technical choices
  2. Follow Deployment Guide to set up your environment
  3. Study API Design to understand system design

Key Documents:

🔧 I'm DevOps/Infrastructure Team

Goal: Understand deployment, infrastructure, and operational requirements

Quick Path:

  1. Start with Tech Stack for infrastructure overview
  2. Review Pulumi Deployment Specification for deployment approach
  3. Study Multi-Tenant Architecture for scaling considerations

Key Documents:

📋 I'm Managing Product/Featurest

Goal: Understand feature roadmap, user needs, and product strategy

Quick Path:

  1. Start with Featurest Overview to understand product capabilities
  2. Review MVP Features for launch scope
  3. Study Stakeholder Experiences to understand user needs

Key Documents:

🎨 I'm Designing User Experience

Goal: Understand user needs, design system, and interface requirements

Quick Path:

  1. Review Stakeholder Experiences to understand our end users
  2. Study User Journeys for experience flows
  3. Explore UI Components for design system

Key Documents:

🔍 I Need to Understand Our Target Customers

Goal: Learn about the end users we're building for (not internal team members)

Understanding Our End Users:

  • Board Directors: Non-executive directors who need cybersecurity governance oversight
  • Management Teams: Senior executives implementing cybersecurity policies
  • IT Staff: Technical teams executing compliance tasks
  • Compliance Teams: Specialists managing regulatory requirements

Key Customer Documents:

Business Strategy & Market

Technical Foundation

Product & Features

Customer Understanding

Understanding the Business Context

  • Start with Core Principles to understand our strategic approach
  • Read Project Overview for market context and business opportunity
  • Study Target Users to understand who we're selling to
  • Review Value Proposition to understand our competitive advantages

Understanding What We're Building

  • MVP Features define our launch scope and immediate priorities
  • Essential Eight is our core compliance framework and main differentiator
  • Stakeholder Experiences show how end users will interact with the platform
  • Process Documentation details the workflows customers will follow

Understanding How We're Building It

  • Technical Architecture shows our system design approach
  • Technology Stack explains our technical choices and rationale
  • Development Guides provide setup and contribution instructions
  • Implementation Standards ensure consistent development practices

What's New for Internal Teams

Recent Strategic Developments

  • Governance-First Positioning: Confirmed board-level tool rather than technical security focus
  • Australian Market Focus: Specialized approach for Australian regulatory environment
  • Multi-Board Strategy: Directors managing multiple company boards with complete isolation
  • Technology Standardization: Skeleton UI and modern edge computing stack

Recent Technical Progress

  • Architecture Documentation: Complete technical architecture and implementation guides
  • Development Environment: Local development setup and contribution guidelines
  • Security Framework: Multi-tenant architecture with enterprise-grade security
  • Automation Planning: AI agent strategy and n8n workflow automation approach

Recent Product Decisions

  • MVP Scope Definition: Essential Eight framework with director dashboard and basic automation
  • Feature Prioritization: Clear roadmap balancing governance needs with implementation requirements
  • User Experience Strategy: Mobile-first director communication through WhatsApp integration
  • Quality Standards: Comprehensive content quality and consistency frameworks

Getting Support as Internal Team

Business Questions

  • Strategy Questions: Reference Core Principles and Business documentation
  • Market Questions: Review Target Users, Market Analysis, and Value Proposition
  • Customer Questions: Study Stakeholder Experiences and User Journeys

Technical Questions

  • Architecture Questions: Reference Technical Architecture and Implementation guides
  • Development Questions: Use Technology Quick Reference and Development guides
  • Infrastructure Questions: Review Deployment guides and Technical Implementation

Product Questions

  • Feature Questions: Reference Feature documentation and MVP specifications
  • User Experience Questions: Study User Journeys and Design documentation
  • Roadmap Questions: Review Features Overview and Future Features planning

Next Steps for Internal Team Members

After completing this quick start:

  1. Bookmark sections most relevant to your role for quick access
  2. Join development environment setup if you'll be contributing code
  3. Understand our target customers deeply since they drive all our decisions
  4. Reference Core Principles regularly for decision-making alignment
  5. Stay updated through TaskMaster for project progress and task coordination

Welcome to the GetCimple team! This internal documentation is designed to help you understand the business, contribute effectively, and build something valuable for Australian businesses struggling with cybersecurity governance.