Tech & Startups: ready template

Build me an internal operations system (Internal Ops) for a SaaS startup to manage customers, subscriptions and support from one place. The system shows the account list with advanced search and filters, each customer's details (their plan, payment status, activity log), and manual plan management, upgrades, cancellations and refunds where needed. Make the roles and permissions (RBAC) precise: owner, operations manager, support agent and accountant, each role seeing and editing only what their permission allows, with secure login, two-factor authentication and an audit log documenting every sensitive change and who made it. Design the architecture to withstand account growth: a database indexed on the most-searched fields, caching of heavy dashboard results, and task queues (queues) for long operations such as bulk export and notification sending. Apply international security standards: encryption of sensitive data, protection against common attacks (SQL injection, XSS and CSRF), rate limiting, and automatic daily backups. The interface is English-first with Arabic RTL support, responsive and accessible. Add internal monitoring and analytics (observability), error logs and a system-health dashboard. Wire report export to Excel/PDF, and make it production-ready with basic tests and concise documentation for the team.

Build me a self-service customer portal facing users directly, where they sign in to manage their accounts without the support team stepping in. The user can register and verify their account, see their current plan and usage, upgrade or downgrade, update their payment details, download their invoices, and open and follow support tickets. Connect local payments through a gateway (mada, Apple Pay, Moyasar or HyperPay) with an API key stored in the secrets vault, and issue an e-invoice compliant with the tax authority (ZATCA). Apply team-level roles and permissions: the account owner can invite members and set their permissions, with secure login and optional two-factor authentication. Design the front end to handle high loads: a content delivery network (CDN) for static assets, caching of repeated pages and queries, and an indexed database. Apply international security standards: encryption, protection against common attacks, rate limiting and backups. Make it English-first with Arabic RTL support, fast, responsive and accessible, with monitoring, analytics and logs. Make it production-ready with a professional user experience, tests and concise documentation.

Build me an internal workflow automation engine that links product events to automatic actions with no manual work. For example: when a new user signs up, a multi-step welcome path begins (a WhatsApp message, an email, a follow-up task after 3 days); when a subscription nears its end, a renewal reminder goes out; and when a payment fails, a dunning path starts with graduated retries. Make the rules configurable from a dashboard (trigger = the event, the condition, the action) without touching the code, with roles and permissions defining who can create or edit paths, and secure login. Rely on task queues (queues) to execute heavy actions asynchronously, and a scheduler for deferred and recurring jobs, with automatic retries on failure and an execution log for each path (succeeded/failed/pending). Design it to scale to thousands of jobs a day: an indexed database, caching and scalable workers. Connect WhatsApp, email and any external API with keys in the secrets vault. Apply international security standards (encryption, rate limiting, attack protection, backups), an English-first interface with Arabic RTL support, and monitoring, analytics and logs. Make it production-ready with tests and concise documentation.

Build me a customer mobile app with Expo that runs on iPhone and Android, connected to the same API and database as my platform so the user and the account are the same everywhere. The user opens the app, signs in securely (email/mobile + OTP), sees their personal dashboard, their data and their usage in real time, performs the product's core operations, and manages their subscription and payment inside the app via a local gateway (mada, Apple Pay, Moyasar or HyperPay) with a key in the secrets vault and a ZATCA-compliant invoice. Add push notifications for important events (renewal, a support message, a status update), and local caching so the app stays smooth even on a weak network and syncs when the connection returns. Apply roles and permissions and secure login, and design the back end to handle thousands of connected devices: an indexed database, caching, and queues for bulk notifications. Apply international security standards (encryption, rate limiting, attack protection, backups), an English-first interface with Arabic RTL support, a responsive and accessible design, and monitoring, analytics and crash logs. Make it production-ready with a professional user experience, tests and concise documentation.

Build me a multi-tenant back-end (API) platform serving a SaaS product, designed from the ground up to scale to millions of users. Each tenant (client company) has its data logically isolated with its own API keys, a precise roles and permissions system (RBAC) inside each tenant, and secure token-based login (JWT/OAuth) with key rotation. Focus on scalable architecture: a carefully indexed database, partitionable (partitioning/sharding) where needed, separation of reads from writes (read replicas), multi-layer caching for hot queries, task queues (queues) for every heavy and asynchronous operation, and a content delivery network (CDN) for assets and cacheable responses. Design the API to be stateless so it scales horizontally behind a load balancer, with rate limiting per tenant and per key, pagination and API versioning. Apply international security standards fully: encryption in transit and at rest, protection against common attacks, an audit log, and backups with a recovery plan. Add comprehensive monitoring and analytics (observability): metrics, request tracing, and alerts on errors and slowness. Document the API clearly (OpenAPI), make the admin interface English-first with Arabic RTL support, and get everything production-ready with load tests, basic tests and concise documentation.