Mike's Notes
The data is clear on this one. Unfortunately, the current developer interest in NZ and Australia is 3% and 0%, respectively. I also can't find anyone in NZ who has the slightest technical understanding of what I'm doing. But there are plenty overseas, especially in MLOPs. We speak the same language, even if the architecture is radically different. Also, top-grade mathematicians seem to get it. Internally, Pipi 9 uses a lot of maths.
Resources
- https://www.blog.ajabbi.com/2025/10/user-account-types-and-workspace-urls.html
- https://www.blog.ajabbi.com/2025/05/worldwide-cost-of-it-failure-revisited.html
References
- Reference
Repository
- Home > Ajabbi Research > Library >
- Home > Handbook >
Last Updated
02/12/2025
Developer access to Pipi is coming
Mike is the inventor and architect of Pipi and the founder of Ajabbi.
The problem
To launch Pipi 9 with limited resources in 2006, the effort needs to be highly focused on developers who build large enterprise systems and have experienced failure, cost overruns, and staggering complexity. This is for them.
The staggering global cost of annual IT failures on big projects is around $US 3 trillion.
- 15% succeed
- 25% makes no difference
- 60 % fail
Web traffic stats
The steadily growing web traffic statistics of public interest in Pipi 9 are becoming very clear.
Since early 2019, the total traffic stats by country are;
- Singapore 19%
- United States 17%
- Hong Kong 13%
- Brazil 12%
Developer Accounts
The initial paid Developer Accounts will be restricted to those four countries. That also affects the language, currency, hours of support availability, etc. Later, as interest and resources grow, that list of countries can be expanded.
Personal Accounts
The free Personal Accounts will initially use an English interface and will not be restricted by country of residence. They will get community support.
Enterprise Accounts
The initial paid Enterprise Accounts will be supported by their associated Developer Accounts, who can charge them for that service. They will initially use an English interface and will not be restricted by country of residence. Developer Accounts will be able to translate UI and documentation into any language and writing system.
Pipi 9 is in hiding
This engineering blog and the many other Ajabbi documentation websites are deliberately hidden from search engines. People are visiting because they are curious, as I write notes to myself and build, learning as I go. It is not easy to find the technical documentation unless you are interested and very determined. That has helped me find some early, keen technical fans who provide testing and feedback. It has also protected me from being overwhelmed by enquiries.
Communication constraints
I am a very slow writer, using assistive technology, have hearing problems and prefer video chats with people who speak good, clear English. I don't speak any other language apart from tiny bits of Maori, French and Spanish.
SEO and GEO
The SEO/GEO settings will be fixed when
- Pipi 9 matures and becomes ready for public use
- Community support is in place
- Bugs fixed
- Enough self-help documentation to help people get started.
Developer Account waitlist
There will be a signup queue to control demand, so scaling is steady with a positive resource feedback loop to solve the chicken-and-egg problem. The small queue is growing now. I will pick the best candidates with the highest chance of success. They will gain a first-mover advantage in building large, custom enterprise systems faster and at a much lower cost. The first ones will get free unlimited support.
Relying on word-of-mouth recommendations.
There will be no marketing or sales, just good, clear documentation, live demos, and bookable office hours (NZ daytime) for having a chat.
Inflexion point
In the future, as workspaces mature and Pipi 10 becomes even easier to work with, resource constraints will disappear, and an inflexion point will be reached.
No comments:
Post a Comment