`

From Accountant to SaaS Founder: Architecting a Full-Stack ERP with CodeIgniter 4

Hello DEV Community! 👋

My name is Ajay. For over four years, I worked as a professional accountant, managing complex financial workflows. During this time, I noticed a recurring problem: small and medium-sized businesses struggle because their operations are scattered across different, disconnected software. HR uses one tool, the sales team uses another, and accounting is stuck trying to reconcile the data.

I realized that the best way to solve a business problem is through solid software architecture. Combining my domain expertise in finance with my passion for full-stack development, I started building a unified solution. Today, I want to introduce you to Acconova ERP, a comprehensive SaaS platform I built from the ground up.

The Core Modules

The goal of Acconova is workflow automation and centralized data management. The system is divided into four integrated core modules:

• HR Management: Automating payroll, attendance mapping, and employee data.
• Accounts: Seamless ledger management, automated invoicing, and financial reporting.
• CRM: Tracking client interactions and managing relationships efficiently.
• Sales: End-to-end sales pipeline tracking, from lead generation to final billing.

The Tech Stack Behind the SaaS

As developers, we know that choosing the right stack is critical for scalability and security. Here is what powers the backend and frontend of this ERP system:

• Backend Framework: PHP with CodeIgniter 4. I chose CI4 for its lightweight footprint, excellent performance, and straightforward routing system.
• Database Architecture: I utilize both MySQL and PostgreSQL depending on the specific module requirements, ensuring complex joins and financial data queries run at lightning speed.
• Server Environment: Deployed on a secure VPS server, utilizing custom subdomain architecture to isolate client environments for better security.

The Biggest Challenge: Database Schema Design

One of the hardest parts of building an ERP is the database schema. When an employee takes a leave (HR module), it needs to automatically reflect in their monthly payout (Accounts module). Designing normalized, interconnected tables without compromising query speed was a massive learning curve, but totally worth it.

Looking Ahead

Building a SaaS product as a solo founder is challenging but incredibly rewarding. I am currently focusing on optimizing the pre-launch marketing strategies and refining the UI/UX based on early feedback.

If you are interested in SaaS architecture, ERP systems, or want to see the platform in action, you can check it out here: Visit Acconova ERP.

I would love to hear from the community! Have you ever built software for the financial or HR sector? What were your biggest architectural challenges? Let me know in the comments below!

`