We partner with boutique agencies, regional engineering shops, and niche specialists who want to pool resources on a common client. NDA-first. Non-exclusive. Reviewed in 5 business days.
Looking for our technology stack instead?
We lead with delivery partnerships — pooling engineers on a joint client engagement. Referral and technology alliances are also open.
Pool engineers on a joint client engagement. We co-deliver as one team.
Refer leads to us; we deliver. You earn structured commission.
Embed Swenivis products (HRMS / GEO / TalentHub / AI Audit) into your solutions — or we embed yours into ours.
Co-delivery only works when both sides have thought through the messy operational parts up front.
Named engagement lead at each company. One person each side owns scope, escalations, and quarterly review.
Weekly cross-PM sync between partner leads. Fortnightly client steering committee with both sides represented.
Every workstream has a documented Responsible / Accountable / Consulted / Informed matrix — no role ambiguity.
Slack channel + shared Linear/JIRA + Git access model defined in sprint 0. Same observability stack.
Explicit choice up front: single brand (one company fronts), co-branded, or sub-contracted. Settled before kickoff.
Defined ladder: PM → engagement lead → executive sponsor at each side. SLAs on response time at each rung.
Billing model
Default: one party bills the client and settles internally (NET-30). Split-invoicing optional when the client requires it.
Rate-card harmonisation
Partners agree to a single converged rate per seniority tier so the client sees a unified commercial proposal.
Revenue split
Set per engagement, not by fixed program-wide formula. Quarterly true-up between partners.
Out-of-pocket recovery
Travel, infra, third-party licences passed through at cost to the client; split per use.
Discount sharing
When one party offers a client discount, the absorber is the one offering it — partner's share stays at quoted rate.
Every joint engagement settles these up front — usually in the MNDA and SOW.
Code, designs, and deliverables built during the engagement → client owns by default. Confirmed in the engagement SOW.
Pre-existing tools, frameworks, libraries each partner brings → each partner keeps their own. Listed in the SOW.
Anything built jointly (e.g. a framework neither side had before) → assigned per engagement. Default: joint with reciprocal use rights.
12-month no-poach of each other's named staff during + after the engagement.
Client information shared between partners under MNDA stays under MNDA. Never shared outside the engagement.
Data processing responsibilities split clearly in the DPA. Each partner is independently responsible for compliance within their scope.
Reciprocal — we share the same documents with you that you share with us.
Drop-in templates partners expect on day one. Rate cards and binding commercials are sent post-MNDA, not in the public kit.
Note: the legal documents below are [TEMPLATE — pending legal review] until our counsel signs them off. Final binding documents are sent to you after MNDA is executed.
Mutual NDA
Swenivis-Partner-MNDA-v1.0.pdf
Template — pending legal reviewPartnership MOU
Swenivis-Partnership-MOU-v1.0.pdf
Template — pending legal reviewJoint Engagement Playbook
Swenivis-Joint-Engagement-Playbook-v1.0.pdf
Template — pending legal reviewMSA Boilerplate
Swenivis-MSA-Boilerplate-v1.0.pdf
Template — pending legal reviewSOW Template (joint)
Swenivis-Joint-SOW-Template-v1.0.pdf
Template — pending legal reviewDPA (DPDP + GDPR)
Swenivis-DPA-v1.0.pdf
Template — pending legal reviewSwenivis Capability Deck
Swenivis-Capability-Deck-Template-v1.0-2026.pptx
LiveDiscovery call
30-min intro to align capabilities and target clients
MNDA signed
Mutual NDA before any rate-card or commercial detail
Capability alignment
Each side shares stack, certs, references
Joint pitch built
Co-authored proposal for a real or hypothetical client
Client win
Contract structure decided (lead-bill vs split-invoice)
Kick-off
Sprint 0 — repos, governance, tooling, RACI
Sprint cadence
2-week sprints, weekly cross-PM sync, joint demos
Handover
Runbooks, ADRs, knowledge transfer to client
Warranty period
60-day post-launch bug fixes on delivered scope
Default is one partner bills the client and settles internally with the other on a NET-30 cycle. Split-invoicing is supported when the client requires it.
The client owns the foreground IP by default. Background IP each partner brings stays with the original owner. Anything jointly invented gets explicit treatment in the SOW — default is joint ownership with reciprocal use rights.
No. The partnership is non-exclusive. Either side can pursue other clients and other partnerships freely. Only the specific shared engagement is governed by the joint SOW.
Whoever registered the lead first (via the Partner Portal once it exists; via email today) gets first right to lead. The other side can be invited in as a sub or skip the engagement entirely.
Yes, with attribution and after Swenivis's review. Joint case studies built during co-delivery require approval from both sides plus the client.
There's no fixed split. Each engagement sets its own split based on resource contribution, client ownership, and commercial responsibility. Documented in the joint SOW.
5 business days. We reply with one of: an invitation to an intro call, an MNDA to sign before deeper conversation, or a polite 'not a fit right now' with reasoning.
Not yet. Tier badges and partner certifications are on the Phase 2 roadmap, once the program has 5+ active partners.
5 business day review · NDA-first · reviewed personally by our partnerships team
