Surfacing data, generating documents, connecting communities through a shared portal, and identifying opportunities to create housing where it's needed most.
KisiBuild brings together community data, organizational intelligence, sales pipeline tracking, document generation, a community portal, and a social feed — purpose-built to identify, win, and deliver housing construction contracts with First Nations communities.
Track bids and proposals from identification through submission to award. Sales pipeline stages, estimated values, RFP tracking, and team assignments with auto-generated proposal numbers (KB-YYYY-XXXX).
Chiefs, council members, band administrators, housing coordinators, decision-makers — all tracked with notes, organization links, and proposal assignments.
200+ entities: First Nations, tribal councils, reserves, Metis locals, government agencies, contractors, and suppliers with hierarchical relationships.
Centralized library for contracts, proposals, RFPs, site assessments, presentations, and reports. Organized per-proposal with categorized uploads.
Thread-based team messaging with member management. Keep sales discussions organized and contextual within the platform.
Meetings, calls, deadlines, site visits, and milestones — all scheduled with attendee tracking and event type categorization.
Build MOUs, offers, contracts, and BCRs from a reusable clause library. Mustache-style variables auto-fill from organization and proposal data. Export branded PDFs with one click.
Blended social feed combining action items, document updates, new proposals, and team announcements. Reactions, comments, and infinite scroll — internal and external versions.
External hub for chiefs, contractors, and investors. Progressive permissions control access to documents, feed, and signing. Invite-token registration with separate session management.
Every module is designed to surface opportunities and support housing development in First Nations communities.
Track each proposal from initial identification through outreach, site visit, estimating, submission, and award. Eight pipeline stages define the sales lifecycle. Estimated contract values and win probability drive forecasting. Sales reps and estimators are assigned per proposal with full RFP tracking.
74 First Nations, tribal councils, reserves, Metis locals, government agencies, contractors, and suppliers — all linked in a parent/child hierarchy. Organizations carry First Nations Profile data (band number, treaty area, reserve number), Community Well-Being scores, housing need assessments, and web presence information.
Track every person across the sales ecosystem — chiefs, councillors, band administrators, housing coordinators, decision-makers, influencers, and funders. Contacts link to organizations with timestamped notes for meeting records and follow-ups.
Upload and organize proposals, RFPs, site assessments, presentations, contracts, and correspondence. Files link to proposals and are categorized by document type for quick filtering and retrieval.
Thread-based messaging keeps sales team conversations organized by topic. The calendar module handles meetings, calls, site visits, milestones, and deadlines with attendee tracking across all event types.
Every create, update, and delete operation is logged automatically with the user, timestamp, entity type, and action. Full accountability and traceability across the entire sales pipeline.
45 reusable clauses organized into six categories — FN commitments, TSD commitments, financial terms, next steps, timelines, and general terms. Select clauses, fill variables like {{fnName}}, {{projectAmount}}, and {{homesPerYear}}, then generate branded PDFs via Puppeteer. Documents flow through DRAFT → SENT → SIGNED lifecycle with auto-generated feed items at each stage.
A blended feed combining action items with social updates — new proposals, document status changes, community announcements, and team posts all in one scrollable timeline. Emoji reactions (👍 ❤️ 🎉 🤝), threaded comments, and cursor-based infinite scroll. Internal feed shows everything; the external portal feed filters to community-visible items only.
Hub-and-spoke network connecting chiefs, contractors, investors, and funders. Each portal user gets progressive permissions — VIEW_DOCUMENTS, SIGN_DOCUMENTS, VIEW_FEED, POST_FEED, VIEW_PROPOSALS — controlled per contact. Invite-token registration, separate session cookie, document signing with IP capture, and a dedicated portal layout with its own navigation.
Five BI dashboards transform raw ISC data, CWB scores, and community records into actionable housing intelligence.
Need scores, Community Well-Being indices, active proposal pipeline status, infrastructure readiness, and geographic factors — all weighted into a prioritized housing need ranking.
Overview stats, community ranking by population, on-reserve vs. off-reserve residency breakdowns, and analysis grouped by tribal council affiliation.
Chiefs and council members, election systems and schedules, term lengths, and governance structures organized by tribal council. Sourced from ISC First Nation Profiles.
Reserve overview, area rankings, grouping by nation and by tribal council. Geographic data including region, service centre, environmental zone, and remoteness index.
Probes all organization websites to identify hosting providers, server technologies, CMS platforms, and SSL status. Understand the digital infrastructure landscape across all communities.
PostgreSQL with Prisma 7 ORM. Every entity connects back to the core Organization model.
Every technology chosen for reliability, developer experience, and long-term maintainability.
Four internal roles with invite-only registration, plus progressive portal permissions for external community members.
| Role | Users & Invites | Proposals | Contacts & Orgs | Documents | Intelligence | Messages |
|---|---|---|---|---|---|---|
| Admin | Full | Full | Full | Full | Full | Full |
| Sales Rep | — | Create / Edit | Create / Edit | Upload / Edit | View | Full |
| Estimator | — | View / Estimate | View | Upload | View | Participate |
| Viewer | — | View | View | View | View | Read |
Admins create invite tokens with pre-assigned roles. Users register via token, set their name and password.
Encrypted HttpOnly cookies via iron-session. 7-day TTL. No JWTs, no local storage exposure.
Token-based with email assignment and 7-day expiry. Single-use, role pre-assigned by admin.
Every API route follows the same conventions. Security is enforced at every layer from middleware to database.
In-memory per-IP rate limiting. Login: 5 req / 5 min. General API: 60 req / min. Returns 429 with Retry-After header.
Zod 4 schemas validate every request body. Structured error responses with field-level messages. Type-safe from request to database.
Global middleware enforces authentication with separate session cookies for internal (kisibuild-session) and portal (kisibuild-portal-session) users. Admin routes get an additional role check. Portal routes validate portal sessions independently.
Every mutation (create, update, delete) is logged with user ID, timestamp, entity type, and action. Complete audit trail for compliance and accountability.
Pagination: ?page=1&limit=20. Search: ?search= (case-insensitive). Filtering: ?status=, ?type=. All responses return { data, total, totalPages }.
Referential integrity enforced at the database level. Deleting a proposal cascades to associated documents, calendar events, and activity logs. No orphaned records.
Portal users sign documents with IP address capture, timestamp, and user agent recording. Documents transition DRAFT → SENT → SIGNED with immutable audit trail. Only DRAFT documents can be edited.
Portal access is permission-based per contact. Admins grant specific capabilities (view docs, sign, post feed) via PortalPermission[]. No blanket access — each feature is individually gated.