Lovable crm program

# Senior Full-Stack Engineer Needed (Lovable + Supabase + Postmark) I'm looking for an experienced senior full-stack engineer to help organize, review, and improve my existing CRM and marketing platform. This is **not** a project to build from scratch. The application is already running and contains a substantial codebase. I'm looking for someone who can understand an existing system, improve its architecture, and help keep it clean and maintainable. ## Tech Stack * Lovable * Supabase * PostgreSQL * TypeScript * Postmark * Zoho Books API * REST APIs ## What I Need ### 1. Project Organization * Review the entire codebase. * Eliminate duplicate logic where appropriate. * Improve project structure and maintainability. * Identify technical debt. * Recommend cleaner architecture without unnecessary rewrites. * Keep the code simple, organized, and scalable. ### 2. Code Audits * Perform read-only technical audits before major changes. * Find potential bugs, edge cases, and inconsistent logic. * Verify that new features integrate correctly with the existing architecture. * Avoid introducing duplicate functionality. ### 3. Postmark Email System I also need someone with strong Postmark experience who can: * Configure transactional email best practices. * Build reusable responsive HTML email templates. * Set up template variables and dynamic content. * Configure message streams. * Improve deliverability. * Set up SPF, DKIM, and DMARC if needed. * Ensure emails display professionally across devices. ### 4. API Integrations Experience with: * Zoho Books API * Webhooks * Background jobs * Scheduled tasks * Email automation * CRM workflows ## Ideal Experience * Strong TypeScript experience. * Supabase and PostgreSQL. * Large existing codebases. * CRM systems. * Marketing automation. * Email infrastructure. * Clean architecture and software design. ## Working Style * Think before making changes. * Understand the existing system before modifying it. * Explain the reasoning behind important architectural decisions. * Focus on quality instead of speed. * Prefer small, safe improvements over risky rewrites. * Communicate clearly. ## Important This project contains real business data. No database changes, migrations, or structural modifications should be made without approval. I value careful planning, technical accuracy, and long-term maintainability over rushing features. If you've worked on complex CRM or marketing platforms and enjoy improving existing systems, I'd love to hear from you. Please include examples of similar projects you've worked on and explain how you typically approach understanding a large codebase before making changes.