---
title: AI Company
description: Learn more about the person behind the website and embark on a journey of inspiration and shared experiences.
canonical: https://www.mandalivia.com/ai-native-company/
---

## What is an an AI-Native Software Company?
- This project is an experiment in building an AI Native Software Company from the ground up.
- What is a company?
	- A company transforms inputs into outputs of higher value and in the process returns a profit.
	- A knowledge company like a software company is performing the transformation in ideas. Specifically we're taking an idea in the form of product requirements, transforms it into 'software' that it then markets to potential customers who pay it for the automation the software provides.
- What are the elements of a company that makes the transformation possible?
	- The company takes inputs in the form of human resources (hiring, training, engaging) software developers, product managers, marketers.
	- The company organizes the human resources into organizational units and sets up processes that enable the groups to communicate. When done right ideas enter through product management, get prioritized against company objectives and transformed into PRDs, development tickets, and marketed through channels.
- An AI-Native Company attempts to rebuild this with AI bots/agents/models that play the steps.

## What is this project?
- This project attempts my journey trying to build an AI-Native Company from the ground up.
- There are two kinds of assets in this site: The current state of the organization and its initiatives. The log of the activities and learnings that resulted in the current state.

## My principles on startups
- Lean principles: Build → Ship → Review
- Start with as simple as you can be.

## Process Documentation
- **Organizational Structure**
  - The company is structured with AI agents filling key roles (Marketing, Product, Operations)
  - Human time (me) is limited to 3 hours per week, acting as CEO/guide
  - Each role has defined responsibilities and expectations

- **Direction Setting**
  - We use OKRs (Objectives and Key Results) to set clear direction
  - OKRs are quarterly and broken down into actionable projects
  - Progress is tracked transparently with regular reviews

- **Meeting Cadence**
  - E-staff Meeting (Weekly): Review overall goals, detect blockers, course-correct
  - Marketing Meeting (Weekly): Execute and review marketing activities
  - Product Meeting (Weekly): Prioritize product development and review progress

- **Work Management**
  - All work is captured in tickets that align with OKRs
  - Tickets include clear goals, implementation details, and time/cost tracking
  - Completed work is documented with lessons learned
  
- **Documentation & Learning**
  - Weekly logs capture progress and insights
  - Experiments are documented with clear hypotheses and outcomes
  - Lessons learned feed back into process improvements

### OKRs & Tickets
- [OKR-1-Launch the site](OKR-1-Launch%20the%20site.md)
- [ticket-slp-contact](tickets/ticket-slp-contact.md)
- [ticket-sitemap](tickets/ticket-sitemap.md) 

## Keep Up With This Project
- **Current Status**
  - Browse [active OKR](OKR-1-Launch%20the%20site.md) to see what we're focused on
  - Review [completed tickets](/ai-native-company/tickets/ticket-sitemap) to see our implementation progress
  - Check our [E-staff meeting notes](/ai-native-company/Meeting-Estaff) for strategic decisions

- **Follow the Journey**
  - Subscribe to our weekly email updates (coming soon)
  - Read our [latest weekly log](/ai-native-company/weekly-logs/May-16-2025) for behind-the-scenes insights
  - See experiments in action like our [Jules AI coding test](/ai-native-company/Jules)
  
- **Learning Together**
  - All documentation is public - learn with us as we build
  - We share both successes and failures transparently
  - The complete journey from concept to implementation is documented