SeaTable Expert for Project Management

🚨 ATTENTION: NO GENERIC AI ANSWERS ALLOWED We use AI tools heavily ourselves, but we will immediately decline any generic, AI-generated proposals. To prove you are a real SeaTable expert, you MUST include the following in your application: The Word "SWISS": Start your proposal with the word "SWISS" so we know you read this. Real SeaTable Proof: Describe one specific system (CRM, Project Management, Inventory) you have personally built inside SeaTable. What were the tables, and how did you link them? Screenshot/Video: Attach an anonymized screenshot or a brief Loom video of a SeaTable base you created. Proposals without visual proof or specific SeaTable details will be ignored. We are looking for an experienced SeaTable specialist who can both set up SeaTable on our own Linux server and design/implement a structured operational cockpit for project and task management. This is not a generic no-code job. We need someone who understands relational data modelling, clean operational workflows, and practical implementation in SeaTable. The first use case is a SeaTable-based cockpit that should become the single source of truth for: customers and internal areas, projects, services, and support channels, tasks, tickets, and backlog items. The core structure is: Customer / Internal Area Project / Service / System Task / Ticket / Backlog Item The cockpit must support: linked records between the core entities, clean relational structure (no critical free-text references where links should be used), task ownership and user-based views, filtered and grouped views, forms for quick capture and full internal ticket handling, attachments and screenshots, optional workflow automations where useful. SeaTable supports linked records, filtered views, automations, and app/table pages, and the self-hosted deployment is Docker-based on Linux. Scope of work We need support in two areas: 1. SeaTable server setup You should be able to install and configure a self-hosted SeaTable instance on a Linux server. Expected tasks: Review server requirements and confirm feasibility. Install and configure SeaTable using Docker / Docker Compose. Configure domain/subdomain, SSL, and basic access. Help with initial admin setup and user access. Ensure the instance is ready for real use, not just a quick demo installation. SeaTable’s official documentation describes a single-node Docker deployment for testing and production, and notes that installation assumes a Linux server with Docker, one domain/subdomain, and open ports 80/443. 2. SeaTable solution design and implementation You should also be able to design and implement the first version of the cockpit inside SeaTable. Expected tasks: Review our implementation brief and challenge it where needed. Propose the final table structure, fields, links, and data model. Build the first working version in SeaTable. Create useful default views for management and team members. Set up forms for quick capture and internal ticket handling. Recommend where automation is useful and where manual workflow is better. Keep the setup clean enough that parts of it could later be migrated into a more custom PostgreSQL-based solution. What we are looking for We are looking for someone who can demonstrate experience with most of the following: SeaTable setup and administration on self-hosted Linux infrastructure, SeaTable bases, linked tables, forms, views, filters, and permissions, relational data modelling, workflow design for project management / task management / ticketing, practical experience with automation, structured thinking and the ability to turn a written brief into a clean working system. Bonus if you also have experience with: n8n or similar automation tools, API integrations, time tracking or operational workflow systems, later-stage migration planning toward custom applications or PostgreSQL. First project phase The first assignment should start as a small paid discovery / implementation sprint, not an open-ended engagement. The goal of the first phase is: validate the final concept, set up the SeaTable server, define the table/field structure, build the first usable version of the cockpit, identify any limitations, risks, or recommended adjustments early. Please include in your application Please answer the following: What hands-on experience do you have with SeaTable specifically? Have you self-hosted SeaTable on a Linux server before? If yes, briefly describe the setup. How would you model a structure like: Customer / Internal Area Project / Service Task / Ticket in SeaTable? How would you implement: task ownership, “My Tasks” views, blocked tasks / dependencies, QA workflow? Which parts would you solve with native SeaTable features, and where would you recommend light automation? Please share relevant examples, screenshots, or short descriptions of similar systems you have built. Important note We are not looking for a generic PM tool consultant or a general no-code freelancer who needs to learn SeaTable from scratch. We are looking for someone who can work hands-on, advise on structure, and implement quickly in a clean and scalable way. Deliverable expectation At the end of the first phase, we expect: a working self-hosted SeaTable environment, a clear and validated data model, an initial working cockpit with linked tables, views, and forms, a short list of recommended next steps. Engagement style We prefer a structured collaboration with clear milestones, concrete deliverables, and short feedback loops.