No-code systems integration — Typeform · Airtable · Softr · Zapier

Kind Profits Survey (KPS) Developer Project Brief No-code systems integration — Typeform · Airtable · Softr · Zapier Kind Systems | Confidential IMPORTANT NOTE TO DEVELOPER This brief is comprehensive and detailed. Please read it fully before scoping or quoting. The methodology, survey structure, scoring model, report design, and app architecture are all specified here. Your job is to build the technical infrastructure around a fully designed product — not to design the product itself. 1. What is the Kind Profits Survey? The Kind Profits Survey (KPS) is an organizational diagnostic tool that collects emotional data from staff to identify where systemic stress is greatest inside a company — and where leadership investment will produce the highest return. KPS is positioned as the next step beyond KPIs. Where KPIs measure outcomes, KPS measures the systemic conditions that produce those outcomes. It is designed for decision makers — CEOs, COOs, and boards — who want to understand why their numbers look the way they do. The survey is structured around 10 clusters of organizational health, each containing 6–8 survey items. Respondents rank their top 2 most frustrating items and top 2 working better items per cluster. Responses are anonymous and tagged by department. The resulting data produces a five-layer report showing organizational stress levels, department breakdowns, and prioritized intervention recommendations. 2. Business model and client tiers KPS operates on two service tiers: Tier 1 — Done-for-you The KPS owner (our client) administers everything. They set up the survey, distribute it, collect responses, and deliver the report. The app does the heavy lifting automatically. Tier 3 — Done-with-you The client company administers the survey themselves through a self-serve portal. The KPS owner interprets results and delivers the report. The client company gets a login to set up their own survey and monitor response rates. Both tiers use the same underlying system. The difference is access level — Tier 1 clients never log in. Tier 3 clients get a restricted admin portal where they can configure their survey and view response progress but cannot see scored results until the report is delivered. 3. The four system components The KPS app has four components that must work together: Component 1 — Admin portal Where the KPS owner (and Tier 3 clients) set up a new company survey. Must handle: • Company name, industry, and tier selection • Department list entry with approximate headcounts • Department grouping for small departments (below 5 expected respondents) • Survey window start and end dates • Generation of a unique anonymous survey link per company • Response rate monitoring dashboard Component 2 — Survey engine The respondent-facing experience. Must be: • Accessible via a unique link — no account required from respondents • Fully anonymous — no names or emails collected at any point • Mobile-friendly and fast-loading • Structured as: Welcome screen → Department selector → 10 cluster questions (20 sub-questions) → Thank you screen • Configured to expire automatically at the survey window close date • Built in Typeform (preferred) or Tally Component 3 — Data engine The scoring brain of the system. Must: • Receive survey responses automatically from Typeform via Zapier or native integration • Apply the weighted scoring model (see Section 5) to every response • Aggregate scores by cluster and by department • Flag departments with fewer than 5 respondents for the listening session protocol • Feed scored data to both the report generator and the benchmark database • Built in Airtable Component 4 — Report generator and dashboard The client-facing output. Must produce: • A live web dashboard with five report layers (see Section 6) • A downloadable PDF version of the same report • Secure client login — each company sees only their own data • Dashboard built in Softr connected to Airtable • PDF generation via Documint or Pdfmonkey connected to Airtable 4. The survey structure Every KPS survey has the same structure regardless of client company. There is no customization of questions — the master question bank is fixed. Survey flow 1. Welcome screen — anonymity statement and estimated time (10 minutes) 2. Department selector — dropdown of the client's department list 3. 10 cluster questions — each cluster has two sub-questions (see below) 4. Thank you screen — confirmation of submission The two-way question format For each of the 10 clusters, there are two multiple choice questions: Question A From this list, select up to 2 items that frustrate you most in [cluster name]. (Multiple choice, max 2 selections) Question B From the same list, select up to 2 items that are working better. (Multiple choice, max 2 selections) The item list for both questions is identical within each cluster. The same item cannot be selected in both Question A and Question B — this constraint must be enforced in the survey logic. The 10 clusters and item counts # Cluster Items Sub-questions 1 Leadership & management 8 2 2 Communication & information flow 7 2 3 Workload & resources 7 2 4 Compensation & financial fairness 6 2 5 Culture & psychological safety 8 2 6 Systems & processes 7 2 7 Technology & tools 7 2 8 Staff development & training 7 2 9 Physical environment & supplies 6 2 10 Strategic direction & change 7 2 Total survey questions: 1 department selector + 20 cluster sub-questions = 21 questions. Estimated completion time: 8–12 minutes. 5. The scoring model Every response is scored using a weighted point system. The data engine must implement this model exactly. Most frustrating #1 3 negative points assigned to that item for that respondent Most frustrating #2 2 negative points assigned to that item for that respondent Working better #1 3 positive points assigned to that item for that respondent Working better #2 2 positive points assigned to that item for that respondent No selection 0 points — respondents may select fewer than 2 on either side Cluster stress index calculation For each cluster, per department and org-wide: • Sum all negative points across all respondents for that cluster • Sum all positive points across all respondents for that cluster • Net stress score = total negative points minus total positive points • Stress index (0–10) = net stress score divided by maximum possible net stress score, multiplied by 10 • Maximum possible net stress = (number of respondents × 2 questions × 3 points per question) Stress index thresholds Score range Status Report color Meaning 7.5 – 10.0 Critical Red Urgent intervention required 5.5 – 7.4 Elevated Amber High priority attention needed 3.5 – 5.4 Moderate Green Monitor and maintain 0.0 – 3.4 Healthy Teal Sustain and learn from 6. The five-layer report The KPS report has five layers. All five must be generated automatically from Airtable data and displayed in the Softr dashboard and PDF report. Layer 1 — Organizational overview and heat map • Four summary metric cards: total respondents, org stress index, highest stress cluster, strongest cluster • Heat map showing all 10 clusters with stress index scores, color-coded by threshold • Each cluster row shows both frustration bar and working better bar Layer 2 — Cluster deep dives • One page per cluster (10 total) • Item-level breakdown showing frustration percentage and working better percentage for each of the 6–8 items • Top 3 frustrations and top 3 working better items highlighted • Systemic interpretation — pre-written diagnostic text per cluster (stored in Airtable, not generated dynamically) • Recommended intervention pointing to Kind Systems or 3D Problem Solving Layer 3 — Department breakdown • Cluster stress scores segmented by department • Departments with fewer than 5 respondents excluded from this layer and flagged • Clickable/filterable by department in the web dashboard Layer 4 — ROI and intervention priority summary • Clusters ranked by stress index — highest to lowest • Each cluster linked to a recommended Kind Systems or 3D Problem Solving intervention • Urgency rating: Immediate / Urgent / High / Monitor Layer 5 — Flagged department listening session guide • Lists all departments below the 5-respondent threshold • Includes the full listening session guide — principles, question script, what to avoid, follow-up guidance • This layer appears only when at least one department is flagged 7. Anonymity and data requirements CRITICAL — ANONYMITY IS NON-NEGOTIABLE The KPS is built on a promise of complete anonymity to respondents. No names, emails, or identifying information may be collected at any point. Department is the only tag applied to a response. Any system design that risks identifying individual respondents is unacceptable. • Department is the only respondent identifier — selected from a dropdown, never entered as free text • Any department with fewer than 5 respondents must be excluded from department-level reporting • Excluded department data is included in org-wide totals only • Client companies must not be able to see each other's data under any circumstances • Response data must be stored securely and not shared with third parties • Survey links must expire at the survey window close date 8. Recommended tool stack Survey engine Typeform (preferred) or Tally — anonymous survey delivery Data storage & engine Airtable — response storage, scoring logic, aggregation Web dashboard Softr — client-facing report dashboard connected to Airtable PDF generation Documint or Pdfmonkey — automated PDF from Airtable data Automation / glue Zapier or Make — connects Typeform responses to Airtable automatically Admin portal Softr (restricted view) or a simple Airtable interface for survey setup You are welcome to suggest alternatives to any of these tools if you have strong reasons and equivalent capability. Please flag this in your proposal. 9. What already exists The following have already been designed and are available to the developer: • Complete master question bank — all 70 survey items across 10 clusters with diagnostic interpretations • Weighted scoring model — fully specified in Section 5 above and in the accompanying Excel scoring template • Report layer designs — interactive prototypes of all five report layers exist as design references • Excel scoring template — a complete working spreadsheet showing the scoring logic, cluster calculations, department summary, and report summary ready for reference • Listening session guide — complete Layer 5 content ready to embed • System architecture diagram — four-component data flow diagram All of these will be shared with the selected developer at project start. 10. Scope of work In scope • Build and configure the Typeform survey with all 10 clusters and 20 sub-questions • Build the Airtable base with response tables, scoring formulas, department aggregation, and threshold flagging • Connect Typeform to Airtable via Zapier or native integration • Build the Softr client dashboard with all five report layers • Configure client data separation so each company sees only their data • Set up the PDF report template in Documint or Pdfmonkey • Build the admin portal for survey setup and response monitoring • Configure the two-tier access model (Tier 1 and Tier 3) • Test the complete end-to-end flow with sample data • Provide documentation for non-technical operation of the system Out of scope • Custom code or custom-built software — this is a no-code build only • Ongoing maintenance beyond a 30-day post-launch support period • Design of survey questions, scoring methodology, or report content — these are provided • Marketing website or public-facing landing page 11. Questions to answer in your proposal Please address the following in your proposal: 5. Can you show a previous project where a survey fed into a database that generated a report or dashboard? Please share a link or screenshot. 6. Do you have experience with both Airtable and Softr together in a client-facing application? 7. How would you handle client data separation in Softr — meaning how do you ensure Company A cannot see Company B's data? 8. What is your proposed approach to the two-question per cluster constraint — preventing the same item being selected as both most frustrating and working better? 9. What is your fixed project quote for the full scope of work described in Section 10? 10. What is your estimated timeline from project start to a tested, working system? 11. Are you proposing any tool substitutions from the stack in Section 8? If so, why? 12. Hiring process 12. Submit proposal addressing all questions in Section 11 13. Top candidates will be invited to a 30-minute video call 14. Selected finalist completes a paid test task (2–4 hours): build the Airtable scoring logic from the provided Excel template and connect it to a sample Typeform survey 15. Final candidate selected and full project contract agreed We are looking for someone who reads this brief carefully, asks smart questions, and demonstrates they understand both the technical build and the purpose behind it. CONTACT To submit a proposal or ask questions about this project, please respond through the platform where you found this posting. Include 'KPS Developer Brief' in your message subject.