Taskhub SaaS – Project Management Tool, Finance & CRM Tool

Taskhub SaaS: Technical Overview & Architecture

Taskhub SaaS – Project Management Tool, Finance & CRM Tool is a self-hosted PHP application built on the CodeIgniter MVC framework, designed for agency owners, freelance project managers, and internal operations teams who need one consolidated workspace for delivery, billing, and client records. The CodeIgniter routing layer keeps controllers thin and pushes business logic into dedicated models, which prevents query pile-up when dashboards aggregate projects, invoices, and timesheet data simultaneously. Views refresh through asynchronous AJAX request cycles, so task status changes, chat messages, and invoice state transitions update the interface without triggering a full page reload. The data layer runs on MySQL 5.x with normalized relational tables, allowing join-based reporting across projects, staff assignments, and financial records without duplicated storage.

Integration is handled at the module level rather than through external page builders, since the application ships as a standalone CodeIgniter codebase with JavaScript, HTML, CSS, and SQL files bundled together. The centralized administrative panel exposes configuration for company branding, role-based permission matrices, currency and tax settings, and notification routing, all persisted server-side and applied across every workspace instance. Because the platform operates on a SaaS model, tenant-level separation is enforced before module rendering, letting one installation serve multiple client organizations from a single deployment.

Key Functional Features of Taskhub SaaS for Modern Deployments

• Project & Task Management: Projects are decomposed into task hierarchies with assignee fields, due dates, priority flags, and status pipelines; the kanban and list views render from the same model layer so state changes propagate immediately through AJAX postbacks.
• CRM & Lead Management: Lead records capture source, contact details, and follow-up stages, with conversion logic that transfers a qualified lead into a client object and links it to subsequent projects and invoices without re-entering data.
• Finance & Invoicing Module: Invoices are generated from project milestones or timesheet totals, calculate tax and discount fields server-side, and record payment status against each line item for reconciliation against the client ledger.
• Timesheet Tracker: Staff log hours against tasks with start/stop timers and manual entries; the aggregated output feeds both payroll review screens and client-billable reporting without a separate export step.
• Team Chat & Collaboration: An internal chat application routes messages between staff and clients through the application’s AJAX channel, keeping project conversations attached to the relevant workspace context.
• Users & Staff Management: Role-based access controls determine which screens, records, and financial data each user can view, with administrative screens for onboarding staff and defining per-role permissions.

Real-World Deployment Scenarios

• Digital Agency Operations: An agency manages client intake through the CRM module, converts signed leads into projects, assigns developers via task boards, and closes the cycle by issuing milestone invoices from the finance module within the same database.
• Freelance Consultancy Billing: A solo consultant uses the timesheet tracker to record billable hours per client engagement, then generates itemized invoices directly from the logged entries, eliminating manual hour reconciliation at month-end.
• Internal IT & Operations Teams: An internal department deploys the application on a private server to coordinate tickets as tasks, track staff workload through the timesheet view, and produce department-level utilization reports from the relational data layer.

Technical Architecture & Compatibility Standards

The application requires PHP 7.x with MySQL 5.x and runs on standard Apache or nginx configurations with mod_rewrite enabled for CodeIgniter’s clean URL routing. Front-end assets are plain JavaScript, CSS, and HTML, so no build pipeline or node-based toolchain is needed to deploy the codebase to a production server. The included SQL file initializes the database schema, and the CodeIgniter configuration files define environment variables for database credentials, base URLs, and encryption keys.

Browser compatibility extends to legacy environments, with the vendor documenting support as far back as Internet Explorer 7, which matters for organizations running locked-down internal workstations. Because the stack avoids heavyweight front-end frameworks, page payloads stay minimal and the AJAX request cycle handles incremental state updates rather than re-rendering entire views. Developers extending the system can add CodeIgniter controllers and models following the existing MVC conventions, keeping custom integrations consistent with the core module structure.