NOTE

To the Base44 Team,

My name is Kobi Chen, Founder and Owner of Media Deal, a digital development and AI-focused software studio. I work extensively with Base44 on the development of advanced systems, websites, and client-facing applications. I am writing to share several important observations and recommendations based on continuous, real-world use of the platform.

These points are provided with respect and with the intention of contributing to the long-term success and stability of Base44.

1. Pricing Model and Prompt Consumption

The current pricing structure and prompt consumption model have become difficult to justify from a cost–benefit perspective. In practice, my monthly usage has reached approximately $500–$650, and a considerable amount of time is now spent managing credits and balances rather than focusing on development and delivery.

In one recent case, a relatively small task consumed close to 100 credits in a single day, highlighting a growing gap between cost and actual output. For developers building complex systems at scale, this model introduces unnecessary friction and limits efficiency.

2. Loading Experience and Front-End UX

The global loading indicator displayed when entering the homepage or application negatively impacts the user experience.

When delivering fully branded, client-facing systems, end users should not be exposed to or feel the presence of the underlying platform. In its current form, this affects the white-label experience and reduces the overall sense of polish and professionalism.

3. Content Editing, Elements, and Typography Stability

The current content and element editing experience lacks sufficient stability. Updates and changes occasionally result in broken typography, unintended color changes, and disruption to custom layouts.

For professional development environments that rely on precise branding and design consistency, these issues directly impact product quality and client satisfaction.

4. Update Pace, Stability, and Credit Responsibility

I strongly recommend slowing down the pace of changes and updates. Developers are already selling Base44-based products to end clients, and frequent or sudden updates directly affect ongoing projects, delivery schedules, and client trust.

At this stage, the platform itself performs very well as it is. The primary issues encountered relate to bugs during model switching and occasional cases where a model does not function as expected.

When such platform-level issues occur, there should be clear acknowledgment and credit responsibility. Developers should not bear the cost of credits lost due to issues beyond their control.

5. Direct Engagement with High-Usage Developers

I recommend initiating direct communication with developers whose monthly usage exceeds $300. These users can provide accurate, experience-based insights into real operational challenges and opportunities for improvement.

In my case, approximately $650 was spent this month across multiple accounts. Developers operating at this level are not only consumers of the platform, but also active distributors of its value through their own products and clients.

With dedicated tools and tailored packages, developers like myself could significantly expand Base44’s reach within the global web development ecosystem.

In Closing,
Base44 is a powerful platform with strong potential. Continued success will depend on prioritizing stability, aligning pricing with real-world professional use, and recognizing advanced developers as long-term partners rather than solely as end users.

Kind regards,
Kobi Chen
Founder, Media Deal