π§ GetCimple Core Principles¶
This document consolidates our core values, product principles, and development approach into one comprehensive guide for our 3-person startup.
π Purpose: These principles serve as our decision-making compass, ensuring we stay focused on delivering maximum value to our dual target users: board directors who oversee governance and the management teams who implement it.
π Core Values¶
Drawing inspiration from 37signals (Basecamp) principles, these values form the foundation of our approach:
1. π Simplicity Above All¶
- Less is More: Prioritize fewer, well-executed features over numerous complex ones
- Clear Interfaces: UIs must be immediately understandable to time-constrained, non-technical directors
- Focused Solutions: Solve specific governance problems thoroughly
- Reduced Cognitive Load: Our platform should reduce, not add to governance burden
2. π₯ Stakeholder-Centric Design¶
- Director Focus: Features respect directors' limited time and provide clear governance oversight
- Management Empowerment: Tools help management teams effectively "manage up" and demonstrate compliance
- Dual Value Creation: Every feature creates value for both directors and management teams
- Actionable Insights: Information leads directly to clear decisions or actions
- Personal Liability Awareness: Design acknowledges directors' personal liability for governance failures
3. β±οΈ Calm Productivity¶
- Sustainable Development: Build at a pace that can be maintained indefinitely
- Thoughtful Features: Each feature is carefully considered, not rushed to market
- Reduced Noise: Notifications and reports focus only on what requires attention
- Asynchronous by Default: Our team and product embrace asynchronous work patterns
4. π€ Sustainable Value Delivery¶
- Long-Term Partnership Focus: Build enduring relationships with clients
- Transparent Value Creation: Clearly demonstrate the value we deliver
- Resource Efficiency: Make efficient use of our limited development resources
- Stability Over Feature Churn: Prioritize platform stability over rapid feature deployment
5. π οΈ Real-World Utility¶
- Practical Solutions: Favor practical, proven approaches over theoretical ideals
- Developer Happiness: Choose technologies that enhance productivity
- User Outcomes: Success measured by improved governance outcomes
- Technical Freedom: Respect IT teams' expertise - don't dictate technical implementations
π Key Assumptions¶
About Board Directors¶
- Extremely limited time for governance tools
- Many have limited technical expertise
- Regularly switch between different organizational contexts
- Primarily concerned with due diligence and personal liability
- Delegate most tasks but need visibility
About Management Teams¶
- Focused on execution while balancing governance requirements
- Need to translate technical work into governance language
- Benefit from proactively providing governance information
- Implement frameworks but need clear expectations
- Need tools to effectively "manage up" to board level
About Technology & Market¶
- Simple, reliable technology outperforms complex solutions
- Integration with existing tools creates outsized value
- Regulatory pressure on boards is increasing
- Multi-board service creates unique challenges
- Evidence of governance activities is increasingly required
π§ Constraints We Embrace¶
As a 3-Person Startup¶
- Development Capacity: Finite resources require ruthless prioritization
- Support Capacity: Every feature increases support requirements
- Technical Debt Budget: Limited time for managing technical debt
- Documentation Requirements: All features need comprehensive documentation
Technical Requirements¶
- Performance: System must remain responsive with large data sets
- Security: Multi-tenant architecture requires strict data isolation
- Scalability: Architecture must support growth
- Integration: Must work within constraints of third-party APIs
π§ Decision Framework¶
π― The Value Test¶
Before implementing any feature, ask:
- Does this add direct value to both directors and management teams?
- Does this create a win-win relationship between oversight and implementation?
- Does this simplify governance rather than adding complexity?
- Is this the simplest possible solution to the problem?
- Can we maintain this with excellence over the long term?
If the answer to any question is "no," reconsider the approach.
ποΈ The Stakeholder Lens¶
Evaluate every decision through both perspectives:
Director Perspective:
- Is the time investment justified by governance value?
- Is organizational context always clear?
- Does this help demonstrate due diligence?
- Does this enhance governance oversight?
Management Perspective:
- Are expectations clearly defined?
- Does this help communicate to the board?
- Does this reduce duplicate effort?
- Does this translate operations into governance language?
π The Simplicity Check¶
Apply these questions inspired by 37signals:
- Could we remove this? Would users still achieve core goals?
- Could we simplify this? Is there a simpler solution?
- Are we adding value or work? Does this make things easier or just different?
- Would we use this ourselves? If we were directors, would we find this valuable?
π How to Apply These Principles¶
- During Planning: Review features against the Value Test
- During Design: Apply the Stakeholder Lens for balance
- During Implementation: Use the Simplicity Check continuously
- During Testing: Validate alignment with core values
π‘ Inspirations & Attributions¶
GetCimple's philosophy draws from three complementary sources:
37signals/Basecamp¶
Foundation: Calm company philosophy, simplicity focus, and sustainable pace
- Less is more approach
- Sustainable development practices
- Focus on real value over feature count
Swan AI¶
Execution: Proving 3 people can serve thousands through AI leverage
- Scale through intelligence, not headcount
- Meet users in existing tools (WhatsApp)
- AI augmentation enhances human judgment
- Fast feedback loops with continuous improvement
πΊ _Reference: $10M ARR PER EMPLOYEE with AI? This Startup Says Yes._
IndyDev Dan¶
Methodology: Structured AI-assisted development for maximum efficiency
- Documentation as foundation (context is king)
- Comprehensive planning enables autonomous execution
- Human curation with AI implementation
- Self-validating workflows ensure quality
πΊ Reference: Agentic Claude Code: 3 Codebase Folders for TOP 1% AI Coding
Remember: As a 3-person startup, every decision matters. Keep it simple, valuable, and sustainable.