Tasker CRM: A Unified Task-Management and Client-Relationship Platform

Gulfturn Creative previously managed project tasks and client relationships across separate tools. Task boards, client contact records, onboarding questionnaires, and client support tickets were maintained in disconnected systems, which created manual hand-offs, duplicated data entry, and limited visibility into the status of client work. There was no single source of truth linking a client's CRM record to the operational board where their tasks were tracked, nor a dedicated channel for clients to submit support tickets directly into the team's workflow. The team needed one application that could model both the internal task workflow and the external client relationship, with access controls that kept client data isolated from other clients while still allowing internal staff full operational access.

Gulfturn Creative acted as the product owner, designer, and operator of Tasker CRM. The team defined the data model, access-control rules, and workflow logic, and configured the platform's built-in integrations and backend functions to automate hand-offs between CRM, task management, and client communications. Gulfturn also owns the ongoing operation of the platform, including user invitations, board configuration, and client onboarding.

Tasker CRM is a single web application built on Base44, combining four operational areas. First, a Boards module lets staff create project boards with table, kanban, calendar, and timeline views, each board carrying its own column definitions, groups, and status options. Items within boards support dynamic column data, subtasks, task dependencies, time tracking, comments, file attachments, and a priority field. Second, a CRM module manages client records with contact details, website and SSL/domain expiration tracking, deal value, account-manager assignment, and a timeline of interactions. Third, a client-facing portal allows clients to submit support tickets that flow into an internal Ticket Review queue, and to complete onboarding questionnaires. Fourth, an administration layer handles email templates, FAQ management, user invitations, and role-based access. Tasks can be bulk-imported from CSV files using a generated template, with a validation and audit-log workflow.

AI capabilities are exposed through the platform's InvokeLLM integration, which accepts a prompt and optional JSON schema and returns structured or free-text responses. AI is used to support content tasks within the application, such as generating or summarizing text. The integration accepts file attachments and an optional web-search context flag. The application does not use AI to make autonomous decisions about task assignment, client status, or access control; all such decisions are made or approved by a human operator. AI-generated content is treated as draft input subject to human review before use.

Human review and approval are required at every consequential step. Only admin users can create, update, or delete CRMClient, EmailTemplate, QuestionnaireTemplate, FAQ, and ImportLog records. Board and item writes are restricted to the record creator or admins. Client-submitted tickets enter a Ticket Review queue where an account manager must review and accept them before they are added to a board. CSV imports are validated before any record is created, and every import is recorded in an ImportLog with counts and error detail. User accounts are created only through admin-issued invitations, and client status flags are set through dedicated backend functions rather than direct client action.

The application is a React single-page application styled with Tailwind CSS and shadcn/ui components, served by the Base44 backend-as-a-service platform. Data is stored in entities including Board, Item, CRMClient, Interaction, ClientTicketRequest, OnboardingQuestionnaire, QuestionnaireTemplate, EmailTemplate, FAQ, ImportLog, and CrmFollowUp. Each entity enforces row-level security: for example, boards are readable by their creator, assigned client, or admins; CRMClient records are readable by the assigned account manager, the client's own email, or admins; client ticket requests are readable by the submitting client, the assigned account manager, or admins. Server-side backend functions handle operations that require elevated privileges or external coordination, including CSV task import with validation and audit logging, templated email dispatch, onboarding questionnaire delivery, task-assignment and ticket-request notifications, and inbound lead follow-up receipt. Built-in Core integrations provide LLM invocation, email sending, file upload, image generation, speech synthesis, video generation, audio transcription, and structured data extraction from uploaded files.

Access control is enforced through row-level security rules defined per entity. Read, write, create, and delete operations are each governed separately. Client-facing data is isolated so that a client can only see their own tickets, onboarding questionnaire, and portal content. Internal staff with admin role have broader access; non-admin staff see only records they created or are explicitly assigned to. Sensitive configuration such as the account-manager email is stored as an application secret rather than in client-visible configuration. No client or operational metrics are published in this case study; outcomes not yet measured are marked as not_disclosed.

The platform is deployed and operational at task-management-copy-4ea89ea7.base44.app. It supports board creation with multiple views, item management with dynamic columns, CRM client tracking with website expiration monitoring, a client portal with ticket submission, onboarding questionnaires, and CSV bulk import with validation and audit logging. Quantitative outcome metrics such as productivity gains, time saved, or adoption rates are not_disclosed at the time of writing; the platform is in internal use and measured results have not been formally captured.

This case study demonstrates a workflow in which a single application consolidates internal task management, client relationship management, and client-facing support into one access-controlled system. It is relevant to organizations that need to link operational task boards to client records without exposing one client's data to another, and that need a structured intake path for client support tickets and onboarding. The CSV import and audit-log workflow illustrates a repeatable approach to bulk data loading with validation.