Swap Assistant
A reusable starting point for a real brief
Agency projects often share the same difficult plumbing: wallet handoffs, quote normalization, approval messages, transaction states and operational visibility. Swap Assistant brings those flows together so your team can inspect them before choosing whether to reuse them.
This is most relevant when a client already has an audience, a product brief and an identified operator. It is less useful when the brief requires a new exchange matching engine, custody platform, bespoke protocol or an untested network.
Separate your work from the reusable core
We agree what comes from the existing software and what your agency or a separate scope will implement. That division makes estimation and acceptance more concrete without inventing a calendar saving.
- Existing core: wallet connection, quote and fee review, activity and alerts
- Configuration: brand, supported providers and named networks
- Client responsibilities: accounts, legal permissions and infrastructure
- Agency scope: surrounding product, bespoke UX and any additional integrations
A clear client handover
The starting offer covers one brand and one isolated customer-owned deployment. Agree the allowed modifications, source access, acceptance cases and support window alongside your client brief. Additional client deployments, sublicensing and source redistribution require explicit written rights; they are not included automatically.
The client remains the operator and supplies approved provider accounts and secrets. We do not provide liquidity, legal clearance or managed custody. Infrastructure and provider costs are not bundled into a promise of permanently free operation.
Make the pilot easy to evaluate
Send a short, non-confidential brief with the client category, required routes and intended handover. We can begin by email and use the synthetic demo to establish fit; a call is optional.
A useful pilot has named acceptance cases, a deployment boundary and a written defect-correction window. Commercial live Radar feeds remain outside the offer unless data rights are approved; its synthetic demo can be discussed as a capability demonstration.
Questions before a pilot
Can we present it under a client's brand?
Yes, subject to an agreed license and scope for that deployment. The reusable core remains non-exclusive.
Are you replacing our development team?
No. The offer is reusable application software and scoped integration/setup. Your team can own the surrounding product and client relationship under the agreed terms.
Can we resell it to multiple clients?
Not under the default single-deployment scope. Sublicensing, redistribution and additional deployments need explicit written rights.