Showing posts with label Ajabbi. Show all posts
Showing posts with label Ajabbi. Show all posts

Small steps add up

Mike's Notes

A great book about how to use a "systems approach" to grow a healthy, mentally strong attitude.

1 per cent better every day is also my gameplan for Pipi 9. It compounds.

Resources

References

  • Atomic Habits by James Clear. Penguin.
  • The Atomic Habits Workbook by James Clear, published by Penguin, $45.

Repository

  • Home > Ajabbi Research > Library > Subscriptions > 3-2-1 Newsletter
  • Home > Handbook > 

Last Updated

01/03/2026

Small steps add up

By: James Clear
Stuff: 12/01/2026

I’ve been writing at JamesClear.com about habits, decision making, and continuous improvement since 2012. I’m the author of the #1 New York Times bestseller, Atomic Habits, which has sold more than 25 million copies worldwide and has been translated into more than 60 languages. I'm also known for my popular 3-2-1 newsletter, which is sent out each week to more than 3 million subscribers.

At the start of a new year, it’s tempting to aim for big, dramatic changes that promise overnight transformation and shiny, instant results. But according to James Clear, the best-selling author of Atomic Habits, lasting success rarely arrives in a single heroic jolt. Instead, it’s built quietly, steadily, one small choice at a time.

In a new workbook, he explains the power of consistent improvements based around the idea that if you get just 1 per cent better each day, those little gains compound into remarkable results. Small habits are easy to overlook in the moment, but they’re the very building blocks of long-term change.

So, as we step into a fresh year and all the possibility it holds, this feels like the perfect reminder: you don’t need to overhaul your life to make progress.

You don’t need huge motivation or massive willpower. You just need to start small, stay consistent and trust that every tiny step is moving you somewhere bigger.

1 per cent better every day

The typical approach to self-improvement is to set a large goal, then try to take big leaps in order to accomplish it in as little time as possible. Too often, we convince ourselves that change is meaningful only if there is some large, visible outcome associated with it. Whether it is getting stronger, building a business, travelling the world or any number of goals, we put pressure on ourselves to make some earth-shattering improvement that will awe everyone around us.

While this may sound good in theory, it often ends in burnout, frustration and failure. And yet, while improving by just 1 per cent every day isn’t notable (and sometimes isn’t even noticeable), it can be just as meaningful, especially in the long run.

It is so easy to dismiss the value of making slightly better decisions on a daily basis. Sticking with the fundamentals is not impressive. Falling in love with boredom is not exciting. Getting 1 per cent better isn’t going to make headlines.

There is one thing about it though – it works.

In the beginning, there is basically no difference between making a choice that is 1 per cent better or not. (In other words, it won’t impact you very much today.) But as time goes on, these small improvements compound, and you suddenly find a very big gap between people who make slightly better decisions on a daily basis and those who don’t.

Here’s the punch line: if you get 1 per cent better each day for one year, you’ll end up 37 times better by the time you’re done. That’s probably a more massive result than you would ever expect, even from a one-time heroic leap, and yet it’s achievable through just one tiny change a day.

This is why small choices don’t make much of a difference at the time but add up over the long term.

[IMG]

Photo: Edited extract from The Atomic Habits Workbook by James Clear, published by Penguin, $45.

But here’s the thing: if positive compounding is true, then so is the inverse. If you get 1 per cent worse each day for one year, you’ll decline nearly down to zero. The lesson is that what starts as a small win, or a minor setback, grows into something much greater. This is why the first important concept when it comes to behaviour change is the key role of continuous self-improvement. Just one tiny shift can change everything.

If you want to predict where you’ll end up in life, all you have to do is follow the curve of tiny gains and losses and see how your daily choices will compound 10 or 20 years down the line.

This is why it doesn’t matter how successful or unsuccessful you are right now. What matters is whether your habits are putting you on the path toward success. Focus on your current trajectory, not your current results. It’s a much better indicator of where you’re headed.

So stop obsessing over the big and start focusing on the small – it’s the key to building the life you want. Success is the product of daily habits – not once-in-a-lifetime transformations.

Edited extract from The Atomic Habits Workbook by James Clear, published by Penguin, $45.

Ajabbi high-level navigation options

Mike's Notes

Ajabbi is the home of Pipi. Today's task has been to think about the common navigation bar used across Ajabbi.com and make it more useful.

The common navigation bar has been added to the top of this blog website as an experiment.

Resources

  • Resource

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

02/02/2026

Ajabbi high-level navigation options

By: Mike Peters
On a Sandy Beach: 29/09/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Common navigation bar

The ajabbi.com website uses a common navigation bar across all its subdomain sites. It deliberately resembles a ribbon. It's inspired by PostHog's previous website navigation.

For logged-in users, a toolbar will be added to each sub-menu.

The bar comprises 8 menu items, 6 of which are permanent and 2 are contextual. Choosing any permanent menu item brings up a sub-menu and 2 possible contextual menus. There are spaces for a total of 12 contextual menus (6x2).

Sub-menu

There is room for up to 8 sub-menu items.

8 menu items x 8 sub-menu items gives a total of 64 possible sub-menu items.

Existing permanent menu items (6)

  • Ajabbi.com
  • Learn
  • Community
  • Handbook
  • Foundation
  • Research

Existing contextual menu items (12 possible)

  • Developer
  • pipiWiki
  • i18n
  • Project
  • Design

Possible menu items

  • Example
  • i18n
  • API
  • Schema
  • Help
  • Blog
  • Cloud

Audience

Are these menu options helpful for website visitors? Who are the groups by audience/task/need?
  • Ajabbi.com (customers)
  • Blog (readers, curious about why)
  • Community (users)
  • Developers (building stuff)
  • Foundation (supporting open-source)
  • Researcher (standards & science behind Pipi)

Changes to be made to the common navigation bar

Each menu item choice has 2 contextual items.

Ajabbi.com

  • Ajabbi.com
    • About
    • Legal
    • Privacy
    • News
    • Press Releases
    • Pricing
  • Learn
  • Community
  • Handbook
  • Foundation
  • Research
  • Developer
  • i18n

Blog

  • Ajabbi.com
  • Learn
  • Community
  • Handbook
  • Foundation
  • Research
  • Developer
  • Blog
  • Newsletter

Community

  • Ajabbi.com
  • Learn
    • Reference
    • Docs
    • Guides
    • Tutorials
    • Demo
  • Community
  • Handbook
  • Foundation
  • Research
  • Project
  • i18n

Design

  • Ajabbi.com
  • Learn
  • Community
  • Handbook
  • Foundation
  • Research
  • Design
    • Acessibility
    • Components
    • Content
    • Data Visualisation
    • Foundations
    • Objects
    • Style Guide
    • Tokens
    • Usability
  • i18n

Developer

  • Ajabbi.com
  • Learn
  • Community
  • Handbook
  • Foundation
  • Research
  • Developer
    • Reports
    • Support
    • Tools
    • Translate
  • i18n

Learn

  • Ajabbi.com
  • Learn
    • Reference
    • Docs
    • Guides
    • Tutorials
    • Demo
  • Community
  • Handbook
  • Foundation
  • Research
  • pipiWiki
  • i18n

Foundation

  • Ajabbi.com
  • Learn
  • Community
  • Handbook
  • Foundation
    • Mission
    • Board
    • Program
    • Events
    • User Groups
  • Research
  • TBA1
  • i18n

Handbook

  • Ajabbi.com
  • Learn
  • Community
  • Handbook
    • Ajabbi
    • Handbook
    • Design
    • Documentation
    • Engineering
    • Product
    • Publication
    • Teams
  • Foundation
  • Research
  • Design
  • i18n

i18n

  • Ajabbi.com
    • Learn
    • Community
    • Handbook
    • Foundation
    • Research
    • Design
    • i18n
      • Languages
      • Downloads

    pipiWiki

    • Ajabbi.com
    • Learn
    • Community
    • Handbook
    • Foundation
    • Research
    • pipiWiki
      • Recently Added
      • Interaction
      • Toolbox
      • Platform
    • i18n

    Project

    • Ajabbi.com
    • Learn
    • Community
    • Handbook
    • Foundation
    • Research
    • Project
      • Current
      • Planned
      • Completed
      • Workshops
      • Status
      • FAQ
    • i18n

    Research

    • Ajabbi.com
    • Learn
    • Community
    • Handbook
    • Foundation
    • Research
      • Research
      • News & Events
      • People
      • Complex Systems
      • About
    • TBA1
    • i18n

    A Waitlist for Pipi

    Mike's Notes

    Who wants early access and to give valuable feedback in return?

    Resources

    References

    • Reference

    Repository

    • Home > Ajabbi Research > Library >
    • Home > Handbook > Ajabbi > Account Types

    Last Updated

    20/07/2025

    A Waitlist for Pipi

    By: Mike Peters
    On a Sandy Beach: 17/07/2025

    Mike is the inventor and architect of Pipi and the founder of Ajabbi.

    To join the waitlist to try out Pipi, please register your interest using the Google Form below. Access will be available on a first-come, first-served basis, and the number of participants will be limited. You can share this link with others.


    Next Ajabbi project will use MovieLab ontology

    Mike's Notes

    I'm starting to map out the shape of the next project. Please note that everything is subject to change as I learn by trial and error. :)

    Resources

    References

    • Reference

    Repository

    • Home > Ajabbi Research > Library > Subject > Film
    • Home > Handbook > 
    • Home > Learn > Docs > Film
    • Home > Wiki > Ontologies > MovieLab

    Last Updated

    05/07/2025

    Next Ajabbi project will use MovieLab ontology

    By: Mike Peters
    On a Sandy Beach: 05/07/2025

    Mike is the inventor and architect of Pipi and the founder of Ajabbi.

    Ontology

    MovieLab has matured significantly since 2019. The ontology and schema are very easy to follow.

    I will use this project to production test Pipi, importing ontologies and automatically generating entities, by using these engines.

    • Ontology Engine (ont)
    • Boro Engine (bor)
    • Entity Engine (ent)

    They will also receive full documentation and have UI workspaces.

    Art Department

    I previously worked in the art department, so I will build that part of the MovieLab schema. I could also test this on an upcoming 40-minute film, currently in pre-production, in which I'm involved.

    • Art Department
      • Hair
      • Wardrobe
      • Props
      • Sets
      • Greenery

    From MoveLab

    "In the Summer of 2019, MovieLabs, on behalf of its member studios, published a whitepaper called “The Evolution of Media Creation”, which laid out a bold 10-year vision for the adoption of new technologies to aid in content production, post and VFX. The paper, often referred to as the ‘2030 Vision’ has now been broadly adopted by many partner companies and is accepted as the industry ‘north star’ for guiding production technologies towards a shared goal.​

    The original Evolution of Media Creation paper, available as a free download, lays out 10 Principles for a more efficient media pipeline using cloud infrastructure, zero trust security and software-defined workflows. The Principles act not just as a destination, but also a roadmap for how to get there. This roadmap drives the work of MovieLabs and those of our studios and external partners as we work together as an industry to bring the promise of the 2030 Vision forward. ​

    Although the 2030 Vision is a technology roadmap it’s primary focus is in empowering the creative – to be able to achieve more – to be more efficient (replacing repetitive and menial tasks so they can focus on creative tasks), flexible (so workflows can change and adapt to new situations and technologies) and faster (so there’s more of the most precious resource – time)." - MovieLab


    Innovation Accounting in Practice

    Mike's Notes

    Ajabbi is a bootstrapped not-for-profit startup. Which is a tough way to go. Innovation accounting will help. I had an online meeting earlier this year with Tristan Kromer, and I gained valuable insights from him. Kenny was originally a musician.

    The Kromatic resources are testable and strongly maths-based. They also don't make a fetish of Business Canvases like the innovation theatre crowd. The focus is on finding tools that are actually useful in a specific context. If they don't quite work, tweak them so they do, or invent one.

    The Monte Carlo simulation is fantastic.

    Ajabbi will pay for support from Kromatic once it has the financial resources. 

    Resources

    References

    • Reference

    Repository

    • Home > Ajabbi Research > Library > Subscriptions > Kromatic
    • Home > Handbook > 

    Last Updated

    27/06/2025

    Innovation Accounting in Practice

    By: Tristan Kromer & Elijah Eilert
    Kromatic: Copied 25/06/2025

    It is not enough to say, “We’re early stage and we shouldn’t focus on a business plan or metrics.” It is not enough to say, “We’re focusing on qualitative data.” And it is certainly not enough to say, “We’ll figure out how to monetize later.”

    As an early-stage venture, you don’t need a business plan, but you do need a business model from Day Zero.

    You don’t need a financial plan projecting cash flows 4 years out, but you do need a financial model on Day Zero.

    Pointing to examples like Twitter and Facebook and how they found their financial model much later is not a good excuse. Even social media products have clear metrics that they measure in the early stages. Social media and game companies count on the fact that they are acquiring a user’s attention and data, and those are valuable assets that can be quantified and monetized later. But we can measure the user’s attention and willingness to relinquish data right away.

    Social media companies are similar to a mining operation. If you were digging up gold from a mine shaft, no one would complain that you didn’t have a detailed plan and metrics to sell it in the market. We know gold is valuable and we can figure out how to sell it later. The value is clear. We just need to know if there is gold down there and how much.

    To say, “we’re an early-stage mining operation and we don’t need to focus on a business plan or metrics,” would be an absurd statement. We can quantify how deep, far, and fast we’re digging. We can quantify the mineral content of the soil and the geology of the area. No one would accept the qualitative data of a dowsing rod to make a serious mining investment.

    Startups, more than ever, should start with a hypothesis-driven financial model from Day Zero. That is why we use innovation accounting.

    In the last article, we discussed why standard business cases don’t work in an innovation context, and the three principles we need in order to replace the standard business case with something better. In this article, we’ll go through how to actually do it. Using innovation accounting, we can build a financial model that is accurate, true, and testable.

    How to Solve the Problem

    To implement innovation accounting for an early-stage project we need to:

    • Identify assumptions
    • Construct a visual model
    • Build a hypothesis-driven financial model
    • Integrate uncertainty


    Four steps innovation accounting method

    1. Identify Assumptions

    step one - innovation accounting method

    There are a ton of assumptions that we make when starting a new innovation project. Fortunately, there are a number of different templates and frameworks that capture those assumptions, such as the business model canvas and customer personas. But none are as useful to innovation accounting as a Storyboard.

    A storyboard, similar to a user-journey map, maps each step of the user journey from start to finish. This includes hearing about the product or service, actually using it, renewing their subscription, inviting friends, or simply finishing their use and throwing it in the trash.

    Storyboards can be used to organize our assumptions into a clear series of actions that the user must take in order for us to both provide value and capture the revenue (or impact if you are a non-profit organization.) The advantage of a storyboard is that it represents observable moments that we can measure. Frame to frame, step to step, each moment in the user journey transitions into another — and we can measure that conversion rate from moment to moment.

    If the first step of the story is downloading an app, and the second step is signing up for an account, that is a conversion rate we can measure — the % of people who sign up for an account after downloading the app. If the next step is applying a filter to a photo, then we can measure the % of users that apply a filter. From qualitative data about what the customer wants (to take beautiful pictures) we can map out our ideal story to deliver that value on quantitative metrics.

    Even from Day Zero with just a nascent idea, we can create the step by step measurable process by which a person becomes a customer. We may not know the actual conversion rates, but we know what we need to estimate and measure. From there, it is tempting to go straight to a spreadsheet, but sometimes a quick detour will help.

    2. Visual Business Model


    step two - innovation accounting method

    Once you have the basic story down, it’s useful to abstract this into a visual financial model. This really is the same thing as a storyboard where the user’s journey from acquisition to purchase is mapped out. However, we will want to simplify some aspects and include retention (if and how customers buy again) and virality (if and how customers refer their friends to become new customers) which are often left out of the storyboard.

    A storyboard or user-journey map is often too detailed for what we need in our financial model. We don’t need to know what % of users apply a filter to a photo, we need to know how many users upgrade, stick around after four weeks, or purchase something so we can zoom out to the bigger picture and only use the most critical metrics that signify important progress towards our business model.

    Startup Metrics for Pirates is a widely adopted framework with the right level of simplification for the purposes of innovation accounting. The five components of this framework are Acquisition, Activation, Revenue, Retention and Referral (AARRR, hence the pirate name.)

    Acquisition (getting a user to your service or product), Activation (getting the user to have a great first experience and recognize the value), and revenue (getting the user to pay something) should already be on your storyboard. It is only a matter of identifying the step in the storyboard that represents the critical points in your business and thus represent the most useful metrics. This simplified, three-step user journey is often represented as a vertical funnel (although representing it horizontally makes no difference).

    However, Retention and Referral are usually not included. That’s just because a storyboard or user-journey map are typically linear. Assembled with yellow sticky notes, it’s hard to represent retaining a customer or referring a friend (although we’ve seen some creative uses of blue sticky tape). But with a journey simplified into a shorter conversion funnel, loops can be more easily added to show where a user retains or refers a friend from a later stage (such add Revenue) back to Acquisition.

    With an easy-to-understand visual model and these last two Pirate Metrics in place, we’re ready to make the leap to a spreadsheet.

    3. Hypothesis-Driven Financial Model


    step three - innovation accounting method

    A hypothesis-driven financial model sounds complex, but it is not. It can and should be as simple as your visual model. Each step can be converted into a row in a spreadsheet, starting with Acquisition for the top line to represent the consistent number of organic visitors to your website or storefront.

    However, unlike a traditional financial model, the number of visitors is not guessed from month to month and hard coded. Instead, a single assumption sets the number for that variable, and a formula varies the value from month to month in the spreadsheet. That way, if the assumption turns out to be wrong, changing a single cell in the spreadsheet will correct it throughout the model.

    Each subsequent row applies the same logic as the visual model. The % of visitors that activate in your user journey becomes a variable that is held constant from month to month, changing visitors into users. The next row might convert users into paying customers who have taken a trial of your product and decided to buy based on another variable, the % of customers who purchase after trial.

    Referral and Retention loops require a bit more thought as they impact Month 2 based on Month 1, but still only require a couple of additional rows of calculation.

    With minimal effort – most teams take 1-2 hours to do this under guidance – a simple spreadsheet is constructed which is driven by a few variables. Those variables can be updated as more information is available.

    Of course, this is a wild oversimplification. But with startups, start simple. We can add complexity over time.

    With a tech startup, we often don’t even model costs on Day 1 because user growth might be all that matters for a social media app or game. However, costs can be introduced and more complexity added as the company grows.

    This basic model allows us to do some basic scenario testing. We can immediately start testing out different acquisition and retention rates to see what the impact on our growth will be. We can even set certain conditions our business must reach in order to meet our growth targets.

    With a limited number of variables, we can see that if our actual retention rate falls below 20%, our referral rate must increase accordingly if we are to continue to grow. This sort of scenario analysis is basic, but effective for helping early-stage innovation tests set pivot-or-persevere thresholds for their business and start designing tests to establish the actual numbers.

    Although entrepreneurs can dictate the shape of their business model, reality will ultimately dictate what numbers go into the variables.

    Here is a financial modeling template for startups if you would like to try it out.

    4. Integrate Uncertainty

    step four - innovation accounting method

    Lastly, we have to integrate uncertainty.

    Although the basic hypothesis-driven financial model allows us to play around and try out different scenarios, it doesn’t actually tell us what is going to happen or the likelihood of success. But we can do this if we get a little data and integrate uncertainty.

    Statisticians have a few tricks we can adopt here. Hurricane forecasts, baseball games, and even startups can use a technique called the Monte Carlo Method to predict outcomes based on uncertainty.

    Instead of entering a single number into each of our variables, we enter two numbers to represent the range and a distribution curve which tells us the likelihood of any individual outcome within that range. This is not easy.

    For example, I may not know the outcome of rolling two six-sided dice and adding the numbers, but I know for certain that it is between 2 and 12. It’s most likely that it’s 7, but 50% of the time the number will be between X & Y.

    We can make the same estimations with our business model variables. We may not know what price the customer is willing to pay, but we should be able to say that they will pay between $10 and $100. That’s all the information we need to start building a Monte Carlo simulation.

    The math behind choosing the right distribution curve is tricky, and the art of choosing the right range requires a bit of training. But both can be accomplished with a little effort. Building the right spreadsheet is even more complicated, but more and more tools are being created that allow teams to run Monte Carlo simulations right in their spreadsheet or in a specialized application.

    Here is a Monte Carlo simulation example if you would like to try it out.

    In practice, this means that innovation teams and executives can create go / no go criteria for their pivot / persevere decisions. You want your project to be at least 10% likely to reach 1B in revenue? The Monte Carlo simulation can tell you if your project has reached that threshold. If not, you can stop the project with confidence that it would not achieve your goals and move on to test the next idea.

    The output of the Monte Carlo simulation is a chart that shows a range of possible outcomes at any given point in the future and allows you to calculate the likelihood of any individual outcome.

    Lessons Learned

    This process is repeatable and is applicable to all types of business models. It doesn’t matter if it’s B2B, B2C, B2G, a network, a platform, or anything else not yet invented. Building a model from Day One allows innovation projects to make better decisions, make useful predictions, and demonstrate real progress to stakeholders.

    Start by:

    • Identifying assumptions
    • Constructing a visual model
    • Building a hypothesis-driven financial model
    • Integrating uncertainty

    Code of Conduct

    Mike's Notes

    I discovered this excellent plain English code of conduct used by the Simons Foundation. I will use it as the basis for the Ajabbi code of conduct.

    They also have a great "Visiting the Simons Foundation", which could also be reused in future.

    Resources

    References

    • Reference

    Repository

    • Home > Ajabbi Research > Library >
    • Home > Handbook > Ajabbi Research > Code of Conduct

    Last Updated

    21/06/2025

    Code of Conduct

    By: 
    Simons Foundation: copied 21/06/2025

    The open exchange of ideas, freedom of thought and expression, and respectful scientific debate are central to the mission of the Simons Foundation and the Flatiron Institute. These ideals require a community that recognizes and respects the inherent worth of every person.

    Event attendees are required to observe all rules of decorum and show respect for all others present, as befits any professional setting. Conduct that is disruptive, causes discomfort or stress to others, or is highly unusual or disrespectful is grounds for removal from the premises at the Simons Foundation’s discretion.

    Further, we are committed to providing an environment that is free from harassment, bullying, discrimination and retaliation. This includes offensive comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, race, ethnicity, religious (or nonreligious) affiliation, politics or any other personal characteristics.

    We do not tolerate:

    • Bullying, intimidation, personal attacks, harassment, vulgar exchanges;
    • Repeated and/or sustained disruption of talks or other events;
    • Behavior that interferes with another’s full participation;
    • Sexual harassment, unwelcome sexual attention, stalking, harassing, photographing or recording, inappropriate physical contact.

    Those in violation of this Code of Conduct may be subject to immediate action ranging from dismissal from a meeting or event to permanent barring from the Simons Foundation and the Flatiron Institute, as determined on a case-by-case basis by our representatives or leadership.

    Adherence to this Code of Conduct is expected of all staff, visitors and conference participants. The code applies both to in-person behaviors and behavior during use of any other communication channels related to the Simons Foundation or Flatiron Institute, including social media. In addition, the code requires all staff, visitors and participants to respect requests for confidentiality during scientific talks.

    We believe our Code of Conduct is essential to the success of our mission. Mutual respect for one another will stimulate our best impulses and performance.

    If you have any questions, or want to report a violation of this code, please email: codeofconduct@simonsfoundation.org

    Ajabbi Media Unit

    Mike's Notes

    I have recently been attending film industry training workshops.

    Resources

    Repository

    • Home > Handbook > Ajabbi > Media Unit > Strategy

    Last Updated

    02/04/2025

    Ajabbi Media Unit

    By: Mike Peters
    On a Sandy Beach: 14/03/2025

    Mike is the inventor and architect of Pipi and the founder of Ajabbi.

    The recent 2-day script workshop by Script Editor, Claire Dobbin, in Dunedin was excellent, and I learned I shouldn't be a scriptwriter, which is important for me to know.

    I previously made over 40 short-form natural history docos in Christchurch before the earthquake (my roles varied over time and included producer/director/art dept/camera/editor).

    Pipi

    I was NZERN's founder, National President, and architect years ago. I led the team that built Pipi 4, a national platform to support community-led ecological restoration. It had its own small server farm. Pipi 4 was highly successful in New Zealand but was 100% dependent on government funding. It eventually died during the Christchurch earthquakes.

    Since then, I have been rebuilding Pipi to be used again. 

    It has been through multiple versions, as significant challenges were solved, and the internal architecture has become entirely novel.

    It uses multi-agent machine learning, and is much faster, more powerful, and more useful for other industries to make it financially viable. It is optimised for large systems that might have the equivalent of more than 100,000 web pages or hundreds of workspace screens.

    Pipi 9 is cloud software that makes building billion-dollar enterprise systems easier, faster, and on budget. It is focused on massive, socially beneficial systems like health. It is funded by donations and bootstrapping, not investors.

    Start-up

    I have undergone various start-up programs to get my head in the right space, run experiments, and make better decisions. I wish I had understood these things back in the early 2000s. The most helpful reading resources are Steve Blank, Strategizer, IT Revolution, PostHog, A Smart Bear, and Kromatic.

    CreativeHQ, NZTE and Startup Aotearoa have been great for talking things over.

    Ajabbi

    Ajabbi has been established to own Pipi, and any surplus income will go to a non-profit foundation to support users, provide open-source SaaS applications and fund research.

    Starting with video

    As a visual thinker, talking is much easier than writing, so to support users, make online bookings for "office hours" available. Set up an area with good sound and lighting that looks OK on video. I must replace most of my film gear with more useful modern equipment. Access to great equipment is no longer a barrier these days.

    The new battery-powered LED panels are fantastic.

    Media Unit

    If Ajabbi goes well, I intend to eventually set up an entirely self-funded paid media unit as part of Ajabbi Research to provide supporting written and video content. The unit will start slowly, building capacity as needed and resources allow. Eventually, it will also publish books.

    • Recording straightforward YouTube content, explaining and demonstrating how to use the software.
    • Then, interviews with authors and scientists can be filmed.
    • Later, filming historical reenactments similar to the ones in Cosmos by Carl Sagan.
    • Starting with a contractor to make the initial content.
    • Then, as income and audience grow, the capability is moved in-house.
    • All content will be freely available for maximum reuse.

    Other people will be writing, producing, directing, presenting/acting or crewing, though hopefully, I will get to help somewhere. My favourite jobs are related to the art department, including set building and miniatures.

    A business model for Ajabbi

    Mike's Notes

    Here are more notes about what I have been learning.

    Resources

    References

    • Reference

    Repository

    • Home > Ajabbi Research > Library >
    • Home > Handbook > 

    Last Updated

    17/05/2025

      A business model for Ajabbi

      By: Mike Peters
      On a Sandy Beach: 24/02/2025

      Mike is the inventor and architect of Pipi and the founder of Ajabbi.

      The New Zealand Ecological Restoration Network (NZERN) was originally behind Pipi. I was its founder and National President and was responsible for the design of Pipi. Many people helped with the work. Pipi 4 was highly successful in New Zealand. It drove the 17th most popular website in NZ for many years, but it ultimately failed because NZERN was financially dependent on funding from the NZ government. They changed their funding criteria just like the weather. They also demanded processes that got in the way of serving the many users best.

      I didn't have a way to understand the problem at the time. Much later, I discovered business models for businesses and non-profits like NZERN, which can lead to better decision-making.

      In 2016, I realized that Pipi was a decade ahead of its time and an early form of cloud computing. I also realised that if the applications it could run were broader, income could be generated, making it financially self-supporting. Things like health, space, utilities, transport, agriculture, and movies.

      I then discovered Alex Osterwalder, Steve Blank, Eric Reis, and Ash Maurya, who all developed systematic methodologies for achieving success using simple tools called Canvases.

      So, in 2017, while I rebuilt the core of Pipi 4 from memory and called it Pipi 6, I also deep-dived into cloud computing to catch up with recent changes and watched video talks from DevOps teams on better processes. I also systematically studied the experiences of others in launching new products and how to ensure success.

      In 2025, Ajabbi is mission-driven, not a business, and will use the Mission Canvas. However, a small company has been established to collect usage fees and pay bills. All profits will be donated to a mission-driven foundation that supports open-source SaaS applications and users. A separate R&D institution is also planned for the long-term development of Pipi. Each will be quite different and need its own canvas.

      Open Handbooks are also being written, so everything is open.

      You can read the detailed history of Pipi on this blog.

      Payment Service Providers

      Mike's Notes

      Eventually, Ajabbi will need the services of a payment service provider.

      Resources

      References

      • Reference

      Repository

      • Home > Ajabbi Research > Library >
      • Home > Handbook > 

      Last Updated

      17/05/2025

      Payment Service Providers

      By: 
      Wikipedia: 2024

      "A payment service provider (PSP) is a third-party company that allows businesses to accept electronic payments, such as credit card and debit card payments. PSPs act as intermediaries between those who make payments, i.e. consumers, and those who accept them, i.e. retailers."

      "They often provide merchant services and act as a payment gateway or payment processor for e-commerce and brick-and-mortar businesses. They may also offer risk management services for card and bank-based payments, transaction payment matching, digital wallets, reporting, fund remittance, currency exchange and fraud protection. The PSP typically provides software to integrate with e-commerce websites or point of sale systems." - Wikipedia.

      Dogfood anyone

      Mike's Notes

      Ajabbi "eats its own dog food".

      It runs on Pipi 9. I use it every day to do real work.

      I designed it so that I could use it to solve complex problems first. Soon, you will be able to use it, too.

      So, I get to experience any bugs, which motivates me to fix them fast.

      Any SaaS worth anything also eats its own dog food. Many don't, so don't use those ones.

      Resources

      References

      • Reference

      Repository

      • Home > Ajabbi Research > Library >
      • Home > Handbook > 

      Last Updated

      17/04/2025

      Article

      By: Mike Peters
      On a Sandy Beach: 10/06/2024

      Mike is the inventor and architect of Pipi and the founder of Ajabbi.

      words

      htaccess

      Mike's Notes

      I learn something new every day.

      Resources

      References

      • Reference

      Repository

      • Home > Ajabbi Research > Library >
      • Home > Handbook > 

      Last Updated

      17/05/2025

      Article

      By: Mike Peters
      On a Sandy Beach: 19/05/2025

      Mike is the inventor and architect of Pipi and the founder of Ajabbi.

      Ajabbi.com now has a draft website, along with several subdomains.

      The problem to solve was that the domain and each subdomain needed to go into their own separate root directory to simplify FTP uploads. There are 20,000 pages of documentation in pre-rendered HTML to upload, which is not a trivial issue.

      The different websites on Apache Web Server all use the same cPanel to manage them. I have never used Apache before. Pipi 3 and 4 used IIS. So a bit of a learning curve for me.

      "cPanel is web hosting control panel software developed by cPanel, L.L.C. It provides a graphical interface (GUI) and automation tools designed to simplify the process of hosting a web site to the website owner or the "end user". It enables administration through a standard web browser using a three-tier structure. While cPanel is limited to managing a single hosting account, cPanel & WHM allows the administration of the entire server. ..." - Wikipedia

      Plesk

      The version I use is called Plesk.

      The .htaccess file had to have a redirect added and written in Perl, which I have yet to learn, so GreenGeeks provided excellent support and edited the file.

      It was

      RewriteRule ^(.*)$ /subdirectory/$1

      qwq

      RewriteRule ^(.*)$ /ajabbi.com/$1

      And it works perfectly.

      A useful website structure

      Mike's Notes

      Note

      Resources

      • Resource

      References

      • Reference

      Repository

      • Home > Ajabbi Research > Library >
      • Home > Handbook > Publications > Websites

      Last Updated

      17/05/2025

      A useful website structure

      By: Mike Peters
      On a Sandy Beach: 14/05/2025

      Mike is the inventor and architect of Pipi and the founder of Ajabbi.

      The time has come to create public-facing websites for Ajabbi so that people can use the Pipi software. There is a 20,000-page backlog of autogenerated and human-written documentation to put somewhere. Here is an experimental structure to test on people to find out what works best. This structure is likely to change a lot based on feedback.

      • ajabbi.com
      • blog.ajabbi.com
      • developer.ajabbi.com
      • docs.ajabbi.com
      • foundation.ajabbi.com
      • research.ajabbi.com
      • workspace.ajabbi.com

      ajabbi.com

      A website where people can find general information, sign up and log in.

      • About (contact, history)
      • Plans (pricing, features)
      • Support (docs, training, whitepapers, events)

      blog.ajabbi.com

      A website for Mike Peters to write about how Pipi was developed.

      developer.ajabbi.com

      A website where developers can get detailed information about building apps to run on the platform.

      • IDE
      • Samples (GitHub)
      • Technical support
      • Translations

      docs.ajabbi.com

      A website where developers can get technical information about the platform.

      • How to guides
      • Versions
      • Roadmap

      foundation.ajabbi.com

      A website for the non-profit organisation that will get any net income and then redistribute it.

      • Grants

      research.ajabbi.com

      A website about experimental research into complex adaptive systems and machine learning computing.

      • Machine learning algorithms
      • Research publications
      • Core documentation
      • Complex adaptive systems

      workspace.ajabbi.com

      A website about the domain applications, including live demos.

      • Film
      • Health
      • Transport
      • Ecological restoration
      • Production forestry

      The next steps in building these websites

      • Find some low-cost hosting for thousands of static web pages about documentation. (done)
      • Configure email server. (done)
      • Register subdomains. (done)
      • Draft up skeleton websites. (done)
      • Use robots.txt to stop web crawlers, especially Google, from indexing and caching pages likely to disappear. (underway)
      • Upload sample documentation to check site-wide navigation and usability. (underway)
      • Organise some meetings to get public feedback and suggestions for improvement.
      • Repeat the design and test process.
      • Build, test, and deploy a DNS engine to automatically create DNS records via the command line or API at a Domain Registrar.
      • Build, test, and deploy an FTP engine that automatically uploads webpages to a host as they are created by Pipi using the CMS Engine.
      • Render and bulk upload working documentation.
      • Edit robots.txt to allow web crawlers, especially Google, to index and cache pages.
      • Add an XML site map file at the root of each website.