Blog

APO Course Roads hit v0.0.10 last month. It's not a 1.0 release yet - we're still in development and testing. But we've reached some meaningful milestones worth documenting.

49 Automated Tests

The biggest achievement: 49 PHPUnit tests covering critical functionality:

• Database schema and table creation
• CRUD operations for courses, profiles, learning plans
• User authentication and access control
• Form validation and data filtering
• API endpoints and service classes

Why does this matter? Because government software needs to be reliable. When an agency spends $200k/year on career development software, it needs to work.

Tests don't guarantee bug-free code. But they catch regressions. They document expected behavior. They make refactoring safe.

What's Actually Built

Here's what v0.0.10 includes:

Course Catalog Management:

• Categories and subcategories
• Proficiency levels (beginner, intermediate, advanced, expert)
• Modalities (classroom, online, hybrid, self-paced)
• Full-text search and AJAX filtering
• Course status tracking (required, recommended, baseline)

User Profiles & Career Tracking:

• Extended profiles with degrees and certifications
• Experience tracking with manager verification
• Role assignments (supervisor, CDO, mentor)
• Profile completion percentage

Learning Plans:

• Custom learning paths per user
• Course status (not started, in progress, completed)
• Progress visualization
• External course integration

Approval Workflows:

• Training request submission
• Supervisor approval queue
• Comments and notes
• Email notifications (architecture in place)

LMS Integration:

• Abstract connector interface
• Meridian LMS template
• Custom LMS connector pattern
• CLI sync command for automation

Reports & Analytics:

• Training activity reports
• User progress tracking
• Approval workflow analysis
• Excel and PDF export

Technical Architecture Decisions

A few choices that turned out right:

Joomla 5 & 6 Compatibility: We built using modern namespaced architecture, dependency injection, and PSR-4 autoloading. This means APO Course Roads works with both Joomla 5 and the upcoming Joomla 6 without changes.

Database-First Design: We designed the database schema first, then built the UI. This matters for federal agencies that need to integrate with existing HR systems. Clean schema means easier ETL.

Package Installer: APO Course Roads installs as a single package including the component and system plugin. One upload, everything works. Agencies don't need to manually install dependencies.

Sample Data Installer: Includes 250+ realistic entries (courses, users, plans). Agencies can see it working with real-looking data before populating their own.

What's Not Done

Let's be honest about gaps:

• No mobile app: It's mobile-responsive, but there's no native app
• LMS connectors are templates: The architecture is there, but real LMS integrations need agency-specific configuration
• Limited internationalization: English only right now
• No SSO integration yet: Federal agencies need CAC/PIV integration - that's coming

Performance at Scale

One thing we haven't tested: 10,000+ users. Most federal agencies we're targeting have 500-5000 employees. We've architected for scale (database indexes, caching layer, query optimization), but we haven't load-tested at enterprise scale yet.

That's a v1.0 milestone.

What's Next

Immediate priorities:

• Beta testing with interested federal agencies
• CAC/PIV authentication integration
• Real-world LMS connector (probably Meridian)
• Performance testing at scale
• Security audit
• Move from v0.0.10 to v0.1.0 beta

If you're a federal agency interested in career development software built by someone who spent 20 years in government IT, reach out. We're offering beta access.

-ES

Apotentia has focused on plugins, themes, and specialized software for government and enterprises. Today, we're announcing something different: APO Proposer, a cloud-based proposal management platform.

This is our first true SaaS product. Here's why we're building it and what makes it different.

The Market Opportunity

Proposal management software is a proven market:

• Market size: $2.49B in 2024, projected to reach $9.64B by 2034
• Growth rate: 14.5% CAGR (compound annual growth rate)
• Established players: PandaDoc ($19-49/user/month), Proposify ($29-65/user/month), Better Proposals ($13-42/user/month)

Unlike some of our other projects, this market is validated. Companies pay $15-65 per user per month for proposal software. The challenge isn't proving demand - it's building a competitive product and acquiring customers.

What APO Proposer Does

APO Proposer handles the complete proposal lifecycle:

Creation & Collaboration:

• Drag-and-drop editor with content blocks (text, images, tables, pricing)
• 50+ professional proposal templates
• Real-time collaboration with presence indicators
• Comments, @mentions, and threaded discussions
• Approval workflows with custom chains

Client Experience:

• Shareable proposal links with password protection
• Mobile-responsive viewing experience
• E-signatures with legally binding audit trails
• Stripe payment integration for collecting deposits
• PDF export and download options

Analytics & Intelligence:

• View tracking (who opened, when, how long)
• Engagement heatmaps showing attention focus
• AI-powered content suggestions
• Win probability scoring
• Pipeline analytics and reporting

Integration & API:

• CRM integrations (HubSpot, others planned)
• REST API with comprehensive documentation
• Webhooks for custom workflows
• Import/export for bulk operations

Tech Stack: Modern and Production-Ready

APO Proposer is built with proven technologies:

• Backend: Laravel 12 (PHP 8.2+)
• Frontend: Vue.js 3, Inertia.js, Tailwind CSS
• Database: MySQL/PostgreSQL
• Real-time: Laravel Reverb (WebSockets)
• Search: Meilisearch via Laravel Scout
• Payments: Stripe via Laravel Cashier
• AI: OpenAI API integration

We're not building from scratch. We're using battle-tested frameworks and tools that have powered thousands of SaaS applications.

Development Status: 75% Complete

Here's where we actually are:

• 806 tests passing - Comprehensive automated test coverage
• 3,929 assertions - Quality assurance throughout the codebase
• Core features complete: Proposal builder, templates, collaboration, e-signatures, analytics
• MVP timeline: 3-6 months to production-ready launch

We're not announcing vaporware. APO Proposer is in late-stage development with significant functionality already working. The repository is private during active development, but we're building this properly before opening it publicly.

Pricing: Competitive and Transparent

We've analyzed the competition and priced APO Proposer to be competitive while sustainable:

Starter: $15/user/month (annual: $12/user/month)

• 5 active proposals per month
• 10 templates
• E-signatures (unlimited)
• Basic analytics
• Email support

Professional: $29/user/month (annual: $24/user/month)

• Unlimited proposals
• 50+ templates
• Real-time collaboration
• Advanced analytics
• CRM integrations
• API access
• Priority support

Business: $49/user/month (annual: $39/user/month)

• Everything in Professional
• Custom templates
• Advanced approval workflows
• Team analytics
• All integrations
• SSO (SAML)
• Dedicated support

Enterprise: Custom pricing

• Unlimited everything
• Custom integrations
• SLA guarantee
• HIPAA compliance
• Onboarding and training

14-day free trial. No credit card required. 20% discount for annual billing.

Why We Can Compete

Proposal management is competitive. Here's our advantage:

Modern Tech Stack: Laravel 12 and Vue.js 3 provide better performance and developer experience than legacy platforms. This matters for feature velocity.

Developer-Friendly: Comprehensive REST API and webhook support from day one. Most competitors treat APIs as afterthoughts.

AI-First Approach: AI features integrated throughout, not bolted on. Content suggestions, win probability scoring, and proposal improvements are core features.

Fair Pricing: Starter at $15/user/month undercuts competitors while providing real value. Professional at $29/user/month matches market leaders while offering more features.

No VC Pressure: We're building for sustainability, not exit multiples. This means we can focus on product quality and customer needs rather than growth metrics.

Valuation: $150K-$500K

Let's talk honestly about what APO Proposer is worth today:

Pre-revenue status: We haven't launched yet. No customers. No recurring revenue.

Conservative valuation: $150,000

• Development cost method: ~1,500 hours @ $75-100/hour = $112K-150K
• 75% complete with 806 tests and 3,929 assertions
• Production-ready within 3-6 months

Optimistic valuation: $500,000

• Strategic value premium for proven market ($2.49B TAM)
• Established competitors validate customer willingness to pay
• Near-production-ready reduces execution risk
• 2-3x development cost for market-validated product

This isn't hype. It's realistic assessment of a late-stage MVP in a proven market. The challenge is customer acquisition, not product viability.

Revenue Projections: Conservative But Real

Here's what we project for APO Proposer (conservative organic growth, minimal marketing):

• Year 1: $6,336 ARR (17 customers, avg 2 users each)
• Year 2: $20,472 ARR (53 customers, avg 2.5 users each)
• Year 3: $51,420 ARR (113 customers + 2 enterprise deals)
• Year 5: $228,480 ARR (390 customers + 10 enterprise deals)

These assume organic growth only. With targeted marketing investment, actual performance could exceed projections. But we're planning conservatively.

Repository: Private During Development

APO Proposer's GitHub repository is private while we complete development. Why?

• Quality focus: We're building this properly before opening publicly
• Security considerations: SaaS platforms require careful security review before exposure
• Competitive positioning: We're not showing our implementation until launch

When we launch, customers will get tested, production-ready code with clear documentation and ongoing support.

What Makes This Different from Our Other Products

APO Proposer is our first true SaaS product:

• APO Recruit: Joomla/WordPress/Laravel plugins (install on your server)
• APO Course Roads: Joomla component for federal agencies (on-premises)
• APO Thematic: Theme marketplace (downloadable themes)
• APO Proposer: Cloud-hosted SaaS platform (we host, you subscribe)

This changes our business model. Plugins and themes are one-time or annual purchases. SaaS is recurring monthly revenue with ongoing hosting costs. It's different economics.

Why SaaS Now?

Fair question: Why add SaaS complexity when we're still launching plugins and themes?

Three reasons:

1. Predictable Revenue: Plugins and themes have uncertain sales patterns. SaaS provides recurring revenue that's easier to forecast and scale.

2. Proven Market: Unlike some of our experimental projects, proposal management is a validated $2.49B market. We know customers will pay.

3. Product Status: APO Proposer is 75% complete. We've already invested significant development time. Finishing and launching makes more sense than abandoning.

The Honest Challenges

Let's not pretend this is easy:

Customer Acquisition: Getting the first 100 customers is hard. We're competing against established brands with marketing budgets. We don't have either.

Hosting Costs: SaaS means ongoing server costs whether we have 10 customers or 1,000. Plugins and themes don't have marginal costs.

Support Requirements: Cloud platforms require 24/7 uptime and fast support responses. That's harder for a bootstrap operation than plugin support.

Feature Parity: Competitors have been building for years. We need enough features to be credible, but we can't match everything immediately.

Why We Think We Can Win

Despite challenges, we have advantages:

Modern Architecture: Built on Laravel 12 and Vue.js 3, not legacy PHP frameworks. This means faster feature development.

Quality Focus: 806 tests and 3,929 assertions. We're building quality into the product, not retrofitting later.

Bootstrap Patience: No VC pressure means we can grow organically. We don't need 3x year-over-year growth to satisfy investors.

Fair Pricing: Competitive rates with transparent pricing. No hidden fees, no mandatory upsells.

Impact on Apotentia's Business Plan

Adding APO Proposer significantly changes our financial projections:

Asset Valuation: Increases total company assets from $19K-49K to $169K-549K (conservative: +$150K, optimistic: +$500K)

Year 5 Revenue Projection: Increases from $170K-300K to $226K-424K (+$56K-124K from Proposer alone)

Portfolio Diversification: Adds predictable SaaS revenue to balance one-time plugin/theme sales

This makes Apotentia more valuable and more sustainable as a business.

What's Next

Immediate priorities for APO Proposer:

• Complete remaining 25% of core features
• Security audit and penetration testing
• Performance testing at scale (1000+ proposals)
• Beta testing with early customers
• Production deployment to staging environment
• Launch with transparent pricing and 14-day trial

We're aiming for Q1 2026 launch, but we won't rush. Quality matters more than speed.

The Bottom Line

APO Proposer is our entry into cloud SaaS. It's a $2.49B proven market with established competitors and validated customer demand. We're 75% complete with 806 tests ensuring quality.

It's ambitious. It's competitive. It's different from our other products. But it's the right move.

Building proposal management software won't be easy. But we're building it anyway.

If you're interested in beta access when we launch, reach out. We'll be looking for early customers to provide feedback and help shape the product.

-ES

When we first planned APO Thematic, we envisioned it as a Joomla-exclusive theme marketplace. Premium themes, one-click installation, unified marketplace - all built for Joomla sites.

That vision just got a lot bigger.

The Market Reality Check

Let's talk about CMS market share:

• Joomla: ~2.5% of websites (40 million sites)
• WordPress: ~43% of websites (800 million sites)
• Drupal: ~1.5% of websites (20 million sites)

Building exclusively for Joomla meant addressing 40 million potential sites. Adding WordPress and Drupal expands our addressable market to 860 million+ sites - a 20x increase, with WordPress alone representing a 30x market expansion.

We'd be foolish not to support WordPress.

Pricing That Makes Sense

Our original Joomla-only pricing was $49/year for single site, $199/year for unlimited sites. After extensive competitive analysis, we've revised our pricing to be more competitive while maintaining fairness:

Subscription Tiers:

• Single Theme License: $29/year - One theme on one site at a time (you can switch themes anytime)
• Multisite Standard: $119/year - Unlimited sites, one theme per site
• Multisite Pro: $599/year - Unlimited sites, multiple themes per domain (mix and match across your sites)

Custom Theme Services:

• Custom Theme: $1,499/year - Fully custom design based on your wireframes and colors, updates for 1 year
• Exclusive Ownership: $4,999 one-time - Own your custom theme forever, never listed publicly, full source code included

Why $29 Instead of $49?

Competitive analysis showed us the market:

• WordPress leaders: Elegant Themes charges $89/year for unlimited sites with Divi builder
• Joomla leaders: YOOtheme charges €150-529/year, JoomlArt charges $89-299/year
• ThemeForest: One-time purchase at $40-69 per theme (no updates or support after first year)

At $29/year, we're 67% cheaper than competitors while providing a better value proposition: access to 20-30 themes instead of just one. Users can switch themes anytime without additional purchases.

$29/year is also sustainable. At $10/year (our initial consideration), one support ticket would cost more than annual revenue. At $29/year, we can provide quality support and maintain the platform.

Unified Marketplace, Three Platforms

Here's what makes APO Thematic different:

One Subscription, All Platforms: Your APO Thematic subscription works across Joomla, WordPress, and Drupal. Same themes, adapted for each platform's template system. No separate purchases needed.

Consistent Design Language: We're not porting themes between platforms. We're designing themes once, then implementing them natively for each CMS. They'll feel native to each platform while maintaining consistent design quality.

One-Click Installation: Whether you're on Joomla 5, WordPress 6, or Drupal 10, themes install with one click from your CMS admin panel. No FTP, no manual uploads, no configuration headaches.

Theme Library Strategy

We're launching with a focused library:

• 2 free themes: No credit card required, full featured, always free
• 20-30 premium themes: Actually 10-15 unique designs, each with light and dark variants
• Monthly additions: New designs released regularly after launch

We're not launching with 50 mediocre themes. We're launching with 10-15 professionally designed themes that look great and work flawlessly across all three platforms.

The WordPress Opportunity

WordPress is the elephant in the room. It's 30x larger than Joomla's market. But it's also incredibly competitive - ThemeForest alone lists 15,000+ WordPress themes.

How do we compete?

• Subscription access: $29/year for all themes vs. $40-69 per theme
• Ongoing updates: Unlike one-time purchases, subscribers get continuous updates and new themes
• Multi-CMS portability: Migrating from WordPress to Joomla? Your themes come with you
• Quality over quantity: 10-15 professional designs instead of 15,000 amateur templates

Domain Protection: apothematic.com

We've secured the domain portfolio for APO Thematic:

• apothematic.com - Primary marketplace domain
• Plus 6 defensive extensions (.design, .info, .net, .org, .pro, .shop)

The marketplace will eventually live at apothematic.com, providing a dedicated destination for theme browsing, purchasing, and documentation.

Technical Architecture

Supporting three CMS platforms requires careful architecture:

• Theme framework: Core design system implemented once, adapted per platform
• Installation plugins: Native installers for Joomla, WordPress, and Drupal
• Update system: Automatic updates pushed through each CMS's update mechanism
• Licensing validation: API-based license checking (respects privacy, no phone-home tracking)

What We're NOT Doing (Yet)

During strategic planning, we considered several features that we're deliberately delaying:

• AI-assisted theme generation: Interesting concept, but not core value proposition
• Page builder integration: Adds complexity, may conflict with theme system
• WooCommerce/VirtueMart/Drupal Commerce: E-commerce themes require specialized knowledge

These might come later. For now, we're focused on beautiful, professional themes that work reliably across three platforms.

Competitive Positioning

APO Thematic isn't trying to be ThemeForest or Elegant Themes. We're building something different:

• Multi-CMS by design: Not WordPress-first with "maybe Joomla later"
• Subscription model: Ongoing value instead of one-time purchase with expiring support
• Curated library: 20-30 excellent themes instead of 15,000 mediocre ones
• Fair pricing: $29/year competitive with market while remaining sustainable

Development Roadmap

Here's what's ahead:

1. Build theme engine and framework - Core system for Joomla, WordPress, Drupal
2. Design initial theme library - 2 free + 10-15 premium designs
3. Create installation plugins - One-click installers for each CMS
4. Build apothematic.com marketplace - Unified browsing and purchasing experience
5. Launch simultaneously - All three platforms at once, not sequential rollout
6. Monthly theme releases - Continuous expansion post-launch

Why This Matters for Apotentia

APO Thematic represents a significant revenue opportunity:

• Lower customer acquisition cost: WordPress marketplace provides discovery
• Recurring revenue: Subscriptions provide predictable income
• Scalable product: Digital themes have near-zero marginal cost
• Portfolio diversification: Balances enterprise focus of APO Recruit and APO Course Roads

Plus, we get to build beautiful things. That matters.

The Honest Reality

APO Thematic is still in planning. We don't have themes designed yet. We don't have the marketplace built yet. We're documenting our strategy publicly as we build.

Why announce before we're ready?

• Transparency: We're building in public, including the planning phase
• Market validation: If no one cares about multi-CMS themes, better to know now
• Domain protection: We've secured apothematic.com and extensions before launch
• Strategic clarity: Public commitment keeps us accountable to execute

What You Can Do

If you're interested in APO Thematic:

• Reach out: Let us know what kind of themes you need (contact page)
• Custom themes: We're accepting custom theme commissions now at $1,499/year or $4,999 one-time ownership
• Support the mission: Donations help fund development

We're building this deliberately, not rushing to market. When APO Thematic launches, it'll work properly across all three platforms.

The Bottom Line

Expanding APO Thematic from Joomla-only to WordPress and Drupal increases our addressable market 20x. Revising pricing from $49-$199 to $29-$599 makes us more competitive while remaining sustainable.

It's a bigger vision than we started with. But it's the right vision.

Building for three platforms is harder. But serving 860 million+ potential sites instead of 40 million makes it worth the effort.

-ES

Most startup stories focus on product launches and customer wins. This isn't one of those stories. This is about the unsexy but essential work of building financial infrastructure.

Over the past week, we've completed two critical milestones: opening business bank accounts at Grasshopper Bank and activating Stripe payment processing. Here's why these matter and how they fit into our bootstrap funding strategy.

Grasshopper Bank: Built for Startups

We chose Grasshopper Bank for our business accounts because they're designed for technology companies and startups. Unlike traditional banks that see software companies as risky, Grasshopper understands our business model.

We opened two accounts:

• Innovator Business Checking: 1.00% APY (under $25K), 1.35% APY ($25K-$250K)
• Innovator Money Market Savings: 1.55% APY (under $25K), 3.10% APY ($25K+)

These aren't typical business bank accounts. Traditional business checking pays 0.01% interest. Grasshopper's checking pays 1.00%. Their savings account pays 1.55% for balances under $25K, then jumps to 3.10% once you cross that threshold.

The Patient Capital Strategy

Why do interest rates matter for a software company?

Because we're building a reserve fund. The plan is simple but requires patience:

1. Contribute $400/month from personal savings ($200 per paycheck, twice monthly)
2. Build up savings in high-yield accounts earning 1.44% weighted average (80% in savings, 20% in checking)
3. Once the fund crosses $25K, interest earnings accelerate to 2.75% weighted average
4. Eventually, monthly interest income covers operational costs
5. When products generate revenue, combine earnings with interest to become self-sustaining

This is patient capital. No investors to please. No quarterly growth metrics. Just steady, methodical building of financial stability.

Projected Growth

Starting from $1,000 (split between checking and savings), here's how the fund grows:

• Month 6: ~$3,825 total ($2,400 contributions + $18 interest + $400-$800 product revenue)
• Year 1: ~$12,160-$17,560 ($4,800 contributions + $45 interest + $6,300-$11,700 revenue)
• Year 2: ~$30,000-$45,000 (crossing the $25K threshold triggers higher interest rates)
• Year 3-5: Accelerating growth as higher interest rates compound

By Year 5, we project $150K-$175K in reserves, generating $4,300-$4,800 in annual interest at 2.75% APY. That won't cover salaries, but it covers server costs, development tools, and miscellaneous operational expenses.

Stripe Payment Processing: Ready for Launch

We've also activated Stripe for payment processing. This enables:

• Donations: One-time and monthly recurring donations at apotentia.com/donate
• Product sales: When APO Recruit, APO Course Roads, and APO Thematic launch
• Subscription revenue: For recurring product licenses and support contracts

Stripe is industry-standard for a reason. Secure, reliable, well-documented. It handles PCI compliance so we don't have to. It supports one-time payments, subscriptions, and invoicing.

We're not reinventing payment processing. We're using the best tool for the job.

Transparent Pricing Philosophy

Our Stripe integration uses straightforward pricing:

• 2.9% + $0.30 per transaction (Stripe's standard rate)
• No hidden fees or markup
• Donors and customers see exactly what they're paying

We're not adding payment processing fees on top. If you donate $100, we receive $97.10 after Stripe's fee. That's it.

Why This Matters for Product Development

Having payment processing in place removes a blocker. When APO Recruit is ready to launch, we don't need to scramble to set up e-commerce. When a federal agency wants to pilot APO Course Roads, we can invoice immediately.

Financial infrastructure built ahead of need means faster response when opportunities arise.

The Bootstrap Reality Check

Let's be honest about what these milestones actually represent:

What we achieved: Set up bank accounts and payment processing. Basic business infrastructure that most companies complete in week one.

What we didn't achieve: Revenue. Customers. Product launches. Actual business results.

Opening bank accounts isn't a business. It's table stakes. But for a bootstrapped company building deliberately, every piece of infrastructure matters.

Comparison to VC-Backed Path

If we had raised venture capital, this entire blog post would seem absurd. Who writes 1,000 words about opening bank accounts?

VC-backed companies open accounts, activate Stripe, and move on. They have runway. They have multiple employees. They're not trying to build self-sustaining operations from interest income on savings accounts.

But we're not VC-backed. We're building patient capital, one $400 contribution at a time.

What's Next

With financial infrastructure in place, we're focused on:

• Completing APO Recruit development for multi-platform launch
• Beta testing APO Course Roads with interested federal agencies
• Building the APO Thematic marketplace
• Growing the reserve fund toward the $25K threshold
• Actually generating revenue (still the hard part)

Banking and payment processing are solved problems. Product-market fit is still the challenge.

Why Document This?

Most startup blogs focus on wins. We're documenting the entire process - including the boring infrastructure work.

Why? Because transparency matters. If we're asking people to support our mission through donations or product purchases, they deserve to see how we're building this company.

Plus, 10 years from now when (hopefully) Apotentia is a sustainable software company, it'll be interesting to look back at blog posts about opening bank accounts and activating Stripe.

We all start somewhere.

-ES

APO Recruit started as a Joomla-only job board and applicant tracking system. Today, we're announcing support for WordPress and Laravel.

This isn't about abandoning our roots. It's about meeting users where they are.

The Platform Adoption Reality

Here's the honest truth about CMS market share:

• WordPress: ~43% of all websites
• Joomla: ~2-3% of all websites
• Laravel: Popular framework for custom enterprise applications

When we built APO Recruit exclusively for Joomla, we were limiting ourselves to 2-3% of the market. That's sustainable if you're the only game in town. But we're not - there are other job board solutions for Joomla, and many more for WordPress.

If we want APO Recruit to be widely adopted, we need to support the platforms people actually use.

Why Multi-Platform Now?

Three reasons drove this decision:

1. Broader Market Reach

By supporting WordPress, we can reach 15-20x more potential customers. Small businesses, recruiting agencies, and organizations that already have WordPress sites can now use APO Recruit without migrating their entire web presence.

2. Enterprise Flexibility

Laravel support lets us serve enterprise customers who need custom applications. Many organizations build their own platforms with Laravel. Now they can integrate APO Recruit as a recruitment module instead of building from scratch.

3. Competitive Pricing Position

WP Job Openings (the leading WordPress job board plugin) charges $69-$399/year depending on sites. We're pricing APO Recruit 10% below that while offering volume-based fairness:

• Starter: $59/year (1 site, <100 applications/year)
• Professional: $119/year (5 sites, 100-500 applications/year)
• Business: $349/year (unlimited sites, 500-1K applications/year)
• Enterprise: Contact sales (1K+ applications/year, custom solutions)

Volume-based pricing is fairer than per-site pricing. A small nonprofit with 50 applications shouldn't pay the same as a staffing firm with 5,000 applications.

What Stays the Same

The core APO Recruit features work across all platforms:

• Job posting management with custom fields and categories
• Applicant tracking with workflow automation
• Custom application forms per position
• Team collaboration with notes and ratings
• Email notifications and candidate communications
• Reporting and analytics on hiring funnel metrics

We're not building three separate products. We're building one product that works on three platforms.

The Technical Challenge

Supporting multiple platforms means:

• Platform-specific adapters for authentication and permissions
• Different installation and update mechanisms
• UI that matches each platform's design patterns
• Testing across three different environments

This is harder than building for one platform. But it's worth it if it means reaching 15x more potential customers.

Repository Status

APO Recruit's GitHub repository is private during active development. We're building this properly before opening it to the public. When we launch, customers will get:

• Tested, production-ready code
• Clear documentation and installation guides
• Regular updates and security patches
• Support contracts available upon request

We're not doing the "move fast and break things" approach. We're building software for businesses managing their hiring processes. It needs to work.

What This Means for Customers

If you're considering APO Recruit:

• Joomla users: You get a native Joomla component built with modern architecture
• WordPress users: You get a plugin that feels native to WordPress
• Laravel developers: You get a package you can integrate into custom applications

Everyone gets the same core features, fair volume-based pricing, and support.

Competitive Positioning

We're not trying to be the cheapest option. We're trying to be the fairest option.

WP Job Openings charges $69/year for one site. Whether you get 10 applications or 1,000 applications, you pay the same price. That's not fair.

APO Recruit charges based on actual usage. Small organizations pay less. High-volume recruiters pay more. Everyone gets the same features.

What's Next

Immediate priorities:

• Finalize WordPress plugin architecture
• Build Laravel package installer
• Create demo sites for each platform
• Beta testing with early adopters
• Public launch with transparent pricing

We're still in active development, but we're building in public. You can follow our progress on the Projects page.

The Bottom Line

Multi-platform support makes APO Recruit more widely adoptable. Fair volume-based pricing makes it more accessible. Building for three platforms is harder, but it's the right move.

We're building software for the market that exists, not the market we wish existed.

-ES

Building a sustainable software company is a marathon, not a sprint. Here's our straightforward approach to growing Apotentia into something meaningful.

Gecker Development Progress

Our flagship social platform continues to evolve. Current stats:

• Over 1,000 automated tests ensuring reliability
• Hundreds of features combining the best of Reddit, Twitter, and Facebook
• Active development with regular improvements

Gecker represents our vision for social media without the exploitation - a platform built for users, not advertisers.

Financial Strategy

Our approach is simple but deliberate:

• Build savings in high-yield savings accounts
• Create a fund large enough to generate monthly dividends
• Use dividend income to cover operational costs
• Fund developer salaries (including my own, currently self-funded)
• Maintain independence - no venture capital, no shareholders to please

This might seem slow, but it keeps us honest. We build what users need, not what investors demand.

Pie-in-the-Sky Plans

With adequate funding, here's what we want to tackle:

• Privacy-First Search Engine: AI-assisted search with zero tracking, no data sales, and absolutely no ads
• Enterprise Tools: APO Course Roads for federal agencies, APO Openings for hiring, APO Thematic for Joomla sites
• Open Source Contributions: Regular donations to projects we depend on and believe in

Charitable Commitments

When we have consistent revenue, we'll establish regular monthly donations to:

• Wikipedia - essential public knowledge infrastructure
• Joomla - the platform our plugins support
• Other open source projects relevant to our work

We benefit from open source. We should contribute back.

Current Reality

Right now, Apotentia is:

• One person (me, Eric Santiago - US Army veteran)
• A disabled-veteran-owned business
• Self-funded from personal savings
• Building products, not chasing funding rounds
• Focused on creating value before extracting it

What's Next

Keep building. Keep improving. Stay independent. Create software that helps people.

If you want to support this work, you can make a donation (see our contact page for details). Otherwise, just knowing people care about ethical software development is encouragement enough.

-ES

Every startup guide tells you to raise money. Pitch to VCs. Build fast. Scale faster. Exit in 5-7 years.

We're not doing any of that.

The VC Model Problem

Venture capital works great for specific kinds of companies:

• Network effects that require rapid user acquisition
• Winner-take-all markets where second place dies
• Capital-intensive businesses (hardware, biotech)
• Products that need to "blitz scale" before competitors catch up

APO Course Roads doesn't fit any of these categories.

It's enterprise software for federal agencies. The market is large but slow-moving. Procurement cycles are 12-24 months. Each sale is complex and relationship-driven. You don't "blitz scale" federal software sales.

What VCs Would Want

If I took VC money, here's what would happen:

• Hire fast - Build a 20-person team before we have product-market fit
• Spend aggressively - Marketing, sales, conferences, enterprise sales team
• Grow at all costs - 3x year-over-year growth or die
• Exit pressure - Need 10x return in 5-7 years, so acquisition or IPO required

This model optimizes for investor returns, not sustainable business building.

Our Model: Patient Capital

Here's what we're doing instead:

• Self-fund from savings - I'm using personal savings to cover development costs
• Build a reserve fund - Put money in high-yield savings accounts
• Generate passive income - Once the fund is large enough, dividends cover operational costs
• Stay small - No pressure to hire before we're ready
• Build for decades - Not years

This might seem slow. It is slow. But it lets us build the right product instead of the fundable product.

The High-Yield Strategy

Right now, high-yield savings accounts are paying 4-5%. If we can build a reserve fund large enough, the monthly interest can cover:

• Server costs
• Development tools and services
• Eventually, developer salaries (including mine)

This is "patient capital" - no investors to please, no exit timeline, no growth-at-all-costs pressure.

The Honest Truth

Here's what I don't talk about in pitch decks: I've tried the private sector three times in 20 years. Each time, I've struggled to adapt.

About 10 years ago, I worked at a small company for 18 months while they built a map tool with Ruby and Leaflet. The company struggled to find customers. I felt woefully uncertain about how to help. I knew how to build software, but I couldn't figure out the commercialization side. Eventually I went back to government work.

That experience taught me something: I need a business model that plays to my strengths. Federal enterprise software fits - slow procurement, long sales cycles, relationship-driven. As a founder with deep federal experience, I can build products I actually understand for a market I know.

What This Means for Customers

If you're a federal agency considering APO Course Roads, here's what our funding model means for you:

• No pivot risk - We're not going to abandon you for a higher-margin product
• No acquisition risk - We're not selling to a PE firm that cuts support
• No feature pressure - We build what users need, not what drives ARR metrics
• Long-term support - We're building for decades, not exit events

The Downside

There are real disadvantages to bootstrapping:

• Slower development - One person vs. a funded team
• Slower market entry - Can't afford big marketing pushes
• Higher personal risk - My savings, my livelihood
• No safety net - If this fails, I'm back to government work

But I'm okay with these trade-offs. I'd rather build slowly and sustainably than grow fast and flame out.

Will It Work?

I don't know. Hopefully I find a government POC who sees the value in APO Course Roads. Or not.

Either way, I'm going to keep building. That's the advantage of not having investors breathing down your neck.

-ES

When I started building APO Course Roads, I had to pick a platform. WordPress? Too blog-focused. Laravel? Too much custom code for enterprise features. Build from scratch? Too slow when you're self-funded.

I chose Joomla 5. Here's why.

Modern PHP Architecture

Joomla 5 isn't your father's Joomla. It's been completely rebuilt with modern PHP 8.1+ standards:

• Namespaced architecture - PSR-4 autoloading, proper class organization
• Dependency injection - Service containers, not global getInstance() calls
• Type safety - Strict types, return type declarations
• Event system - Subscriber pattern, not old dispatcher

This matters for maintainability. Code written in Joomla 5 looks like modern PHP, not legacy CMS patterns.

Enterprise Features Out of the Box

Building enterprise software from scratch means reinventing wheels:

• User authentication and ACL
• Database query builder with prepared statements
• Form validation and filtering
• Asset management for CSS/JS
• Multi-language support
• Caching layers

Joomla provides all of this. I can focus on building the career development logic, not authentication systems.

Federal-Friendly Licensing

Joomla is GPL v2+. This matters for federal agencies:

• No per-seat licensing fees
• Full source code access
• No vendor lock-in
• Can modify and extend as needed

Agencies can deploy to unlimited users without worrying about licensing audits.

The Technical Reality

Here's what APO Course Roads runs on:

• PHP 8.1+ - Modern language features, improved performance
• Joomla 5 & 6 - Forward-compatible architecture
• MySQL/MariaDB - Standard federal database stack
• Composer - Dependency management
• PHPUnit - 49 automated tests (and counting)

It's a stack that federal IT understands and can support.

Why Not WordPress?

WordPress is great for blogs and small business sites. But:

• Plugin architecture isn't designed for complex enterprise apps
• Custom post types get awkward for non-content data
• ACL is too simple for federal role-based access

For a career development system with courses, profiles, learning plans, approvals, and reports - Joomla's component architecture is a better fit.

Why Not Laravel?

Laravel is excellent. But building everything from scratch means:

• Months of development for admin interfaces
• Building form validation systems
• Creating ACL from scratch
• Frontend template systems

When you're self-funded and building solo, time matters. Joomla gives me a head start.

The Joomla Learning Curve

Joomla isn't as popular as WordPress. Documentation can be sparse for advanced features. I had to dig into source code to understand the event system and service providers.

But that's part of building enterprise software. You learn the platform deeply, and that knowledge becomes a moat.

Forward Compatibility

APO Course Roads is compatible with both Joomla 5 and Joomla 6. How?

• No deprecated APIs
• Modern namespaced architecture
• Dependency injection throughout
• No hardcoded assumptions about CMS internals

This matters for federal procurement. Agencies need software that doesn't break with platform updates.

The Bottom Line

Joomla 5 gave me enterprise-grade architecture without enterprise-level development time. I could focus on building career development features instead of plumbing.

For APO Course Roads, it was the right choice.

-ES

I spent 20 years in federal government as a webmaster and systems administrator. Managed AWS environments hosting 250+ sites with 99.99% uptime. Built custom PHP apps, ETL pipelines, APIs for air-gapped networks. I've seen a lot of software come and go in government.

One thing that's always bothered me: career development tools that don't understand how federal employment actually works.

The Commercial Software Problem

Commercial HR and career development platforms are built for private sector companies. They assume:

• Job titles that make sense across industries
• Career progression that's mostly vertical (up the ladder)
• Compensation based on market rates
• Skills that transfer between companies

None of that applies cleanly to federal employment.

What Federal Agencies Actually Need

Federal career development is different:

• GS/GG grade structures - Not just job titles, but pay grades with specific progression rules
• OPM competency models - Standardized frameworks across agencies
• Qualification standards - Specific education and experience requirements by grade
• Continuing education requirements - CPE for accountants, CLE for attorneys, certifications for IT
• Security clearances - Career paths limited by clearance level and reciprocity

Commercial tools don't have checkboxes for these things. They can't map a career ladder from GS-11 to GS-14 with the right time-in-grade and qualification requirements.

The O&M Problem

Here's something else I learned in 20 years: most government software work is O&M (Operations & Maintenance). This leads to:

• Long lead times for simple changes
• Requirements that drift during 18-month procurement cycles
• Deliveries that miss the mark because needs changed
• Personnel rotation that loses institutional knowledge

What agencies need are products, not services contracts. Something that works out of the box, built by someone who understands federal employment.

Why APO Course Roads

That's why I'm building APO Course Roads. It's not a commercial product adapted for government. It's built from the ground up for federal agencies, by someone who spent two decades inside federal IT.

It understands GS grades. It knows about OPM competencies. It can track clearances and certifications. It maps career ladders the way federal HR actually works.

Will it work? I don't know yet. This is my third attempt at the private sector in 20 years. The last time I tried (about 10 years ago), I worked at a small company building a map tool with Ruby and Leaflet for 18 months. The company struggled to find customers. I felt woefully uncertain about how to help them succeed.

But this time feels different. This time I'm building something I actually understand - software for the federal market I know inside and out. And I'm doing it as a founder, not an employee trying to figure out someone else's product strategy.

Hopefully this time I connect with a government POC who needs what we're building. Or not. Either way, I'm going to keep at it.

-ES