WebisoftTokenization Platform
Settlement / DALP Integration
A Phase 0 MVP scope of work for Novark's investor and issuer apps, built on Settlement's DALP platform — with two team options, pricing, and a clear view of what Settlement handles versus what we build.
Contact William Marchand, Webisoft Technologie Inc.
Overview
Webisoft proposes to design and build Novark's two-sided real-world-asset and digital-securities tokenization platform — an Investor app and an Issuer/Admin app — on Settlement's Digital Asset Lifecycle Platform (DALP) rather than a custom blockchain stack.
Novark needs two coordinated products. The Investor app lets holders discover, subscribe to, and manage tokenized real-world assets and digital securities; the Issuer/Admin app gives Novark's team the controls to onboard issuers, configure offerings, and administer the asset lifecycle end to end. Both apps share a single Novark backend that holds business logic, identity and compliance state, and the data model that ties investors, issuers, and instruments together. This Scope of Work covers the Phase 0 MVP — the foundational build that puts both apps and that backend into production.
Rather than stand up and maintain a bespoke blockchain stack, the platform is built on Settlement (SettleMint) and integrated through its DALP API. Settlement provides the tokenization, ledger, and asset-lifecycle primitives as a managed vendor capability, which keeps Novark out of the business of operating low-level chain infrastructure. The engineering weight therefore sits in two places: the Novark backend that owns Novark's logic and data, and the DALP integration that connects it to Settlement. Across the 88 Phase 0 stories, 49 route from the frontend through the Novark backend and 35 route from the frontend to DALP, with the remainder mixed — so the majority of the build is the Novark backend plus the DALP integration layer, not custom protocol work.
This quote is scoped to Phase 0 — the 88-story, 353-point MVP that delivers the Investor app, the Issuer/Admin app, the Novark backend, and the DALP integration as a working platform. Phase 1 (33 stories / 134 points) and Phase 2 (9 stories / 36 points) are presented as roadmap context only; they are not included in this engagement's pricing or commitment and are sized here purely to show the path beyond the MVP. The numbers, team options, and timeline below describe Phase 0 exclusively, on a Time & Materials basis.
MVP Investment
$375K / $400K–$425K
CAD · lean / faster
Delivery Timeline
3.5–6
months
Phase 0 Scope
88
stories / 353 pts
Team Options
2
staffing models
What Settlement handles vs. what we build
Platform & Architecture
The system is split across two trust boundaries. Settlement/DALP is the platform of record: it owns authentication, identity, claims and compliance attestations, and every token and blockchain operation, including on-chain transaction reads. It is the source of truth for who a user is, what they are permitted to assert, and what has happened on-chain. Webisoft does not rebuild any of this — we integrate against it. The Novark backend is the application layer Webisoft builds on top of DALP: it holds the encrypted PII that DALP deliberately does not store, runs the app-specific workflows and business logic, exposes admin tooling and permissioning, and orchestrates the third-party services the product depends on. In short, DALP is the identity and chain substrate; Novark is the product.
The two communicate through a clean, event-driven contract rather than shared state. The frontend talks to whichever side owns the data — DALP for auth, identity, and on-chain reads; Novark for everything app-specific — and the two backends stay in sync by publishing and consuming domain events. This keeps PII isolated inside Novark's encrypted store, keeps key material and chain authority inside DALP, and gives each side an independent deployment and scaling envelope.
The bulk of the build is the Novark backend plus its DALP integration: of the 88 Phase 0 stories, 49 route Frontend to Novark Backend and 35 route Frontend to DALP (the remainder mixed), so most of the delivered surface area is the Novark application layer wired correctly to the DALP platform.
Settlement / DALP handles
- Auth and sessions — BetterAuth runs on DALP
- Identity and system/profile records — the canonical user record
- Claims and compliance attestations
- Token and blockchain operations — create, manage, transfer
- On-chain transaction reads
Novark backend (we build)
- PII database — encrypted personal data DALP does not store
- App-specific workflows and business logic
- Admin tools and permissioning
- Domain events and notifications
- Third-party integrations and orchestration
Third-party services
FusionAuth / BetterAuth
Authentication and OIDC
SumSub
KYC / identity verification
Twilio
Phone / SMS verification
S3 / object storage
Documents and avatars
Event-driven by design: all 130 stories declare a domain event (e.g. user.registered, user.email_verified) with an explicit publisher — DALP Auth, DALP, or Novark Backend — and a defined payload, so every state change is a contract, not an assumption.
88 stories · 353 story points
Phase 0 MVP Scope
Phase 0 ships the platform's foundational product surface: 88 user stories totaling 353 story points, organized into seventeen epics that together deliver a complete primary-issuance workflow from investor onboarding through issuer administration. The scope is deliberately clustered into three themes — Onboarding & Identity, Investor Experience, and Issuer & Admin — so that each delivers an end-to-end slice of value rather than disconnected features.
Onboarding & Identity
98 ptsHow a user creates an account, signs in securely, completes identity and compliance checks, and manages their profile and security settings — registration, login, email/phone/KYC verification via SumSub, suitability and TOS, and profile with avatar, 2FA and password management.
Investor Experience
104 ptsEverything an investor sees and does post-onboarding — discovering opportunities, reviewing offerings and documents, tracking holdings and activity, and managing their wallet — across the landing/opportunities pages, dashboard, token page, documents, updates, wallet, and transaction history.
Issuer & Admin
151 ptsThe tools issuers and operators use to launch and configure tokens, administer the ongoing token lifecycle, maintain the cap table, onboard existing investors in bulk, and execute operational transfers — create token, manage token, cap table, issuer dashboard, import users, and operational transfers.
| Epic | Theme | Stories | Points |
|---|---|---|---|
| Manage Token | Issuer & Admin | 10 | 47 |
| Verification (email, phone, KYC, suitability, TOS) | Onboarding | 8 | 44 |
| Create Token | Issuer & Admin | 5 | 31 |
| Import Users | Issuer & Admin | 7 | 29 |
| Profile (avatar, 2FA, password) | Onboarding | 8 | 28 |
| Cap Table | Issuer & Admin | 7 | 22 |
| Registration | Onboarding | 4 | 20 |
| Token Page | Investor | 7 | 20 |
| Updates | Investor | 5 | 20 |
| Landing / Opportunities | Investor | 6 | 20 |
| Dashboard | Investor | 5 | 16 |
| Documents | Investor | 4 | 16 |
| Operational Transfers | Issuer & Admin | 4 | 14 |
| Issuer Dashboard | Issuer & Admin | 1 | 8 |
| Wallet | Investor | 3 | 7 |
| Login | Onboarding | 2 | 6 |
| Transactions | Investor | 2 | 5 |
| Phase 0 MVP total | 88 | 353 | |
How the estimate splits
Implementation Buckets
The build divides into five workstreams. Most of the weight sits in the Novark backend and the DALP integration; the frontend tracks the Figma designs, and QA/DevOps runs throughout.
Frontend app
Build the Figma implementation, the investor flow, and the issuer/admin screens, calling DALP directly where possible and routing to the Novark backend otherwise.
Backend app (Novark)
Build the Novark APIs, the encrypted PII database, profile data, admin workflows, notifications, and the event bus.
DALP / Settlement integration
Wire up auth, wallet, identity, claims, token operations, and transaction reads against the DALP API.
Third-party services
Integrate FusionAuth/BetterAuth, SumSub, Twilio, and S3/object storage.
QA / DevOps
Stand up environments, test data, staging, deployment, and monitoring.
Two staffing options
Team & Delivery
Two team compositions bracket the engagement, both including dedicated QA. AI-assisted workflows let us keep the team small for the scope. Both deliver the same Phase 0; the difference is pace.
Lean team + QA
Standard pace · ~4.0–4.5 FTE
- Frontend Engineer1
- Backend Engineer1
- Blockchain / DALP Integration Engineer0.5–1.0
- Project Manager / Tech Lead0.25
- QA Engineerpart-time
Timeline
5–6 months · 20–25 weeks
Planning envelope
$375K CAD
A lower monthly burn and a tighter headcount keep the engagement affordable. The trade-off is a slower pace, stretching delivery across 5–6 months before the product is validated.
Faster team + QA
RecommendedAccelerated pace · ~5.75–6 FTE
- Frontend Engineer2
- Backend Engineer1
- Blockchain / DALP Integration Engineer1
- Project Manager / Tech Lead0.5
- QA Engineerpart-time
Timeline
3.5–4.5 months · 14–17 weeks
Planning envelope
$400K–$425K CAD
Adding a second frontend engineer and a dedicated DALP integration engineer compresses the schedule to 3.5–4.5 months, getting to validation sooner. Recommended: quicker delivery shortens time to market and de-risks the build at a comparable total cost.
Roles
Frontend Engineer
Translates Figma designs into a responsive, functional UI.
- Implement investor and issuer user flows
- Build dashboards, token galleries, and profile management screens
Backend Engineer
Builds the core Novark application logic, APIs, and database.
- Manage PII and sensitive user data securely
- Implement admin workflows, notifications, and event handling
Blockchain / DALP Integration Engineer
Connects the platform to the Settlement/DALP infrastructure.
- Integrate authentication, identity, and wallet services
- Implement token and blockchain operations via DALP
Project Manager / Tech Lead
Oversees execution, planning, and technical guidance.
- Manage sprints and the timeline
- Serve as the primary technical point of contact
QA Engineer
Ensures quality and stability through rigorous testing.
- Develop and execute test plans
- Validate functionality against user stories near milestone deliveries
Time & Materials · CAD
Investment
All figures in CAD on a Time & Materials basis. The estimate is built on a transparent daily rate: $800 / day / person across 20 working days / month = $16,000 / person / month. Two staffing models bracket the engagement.
| Option | Timeline | Monthly | Range | Envelope |
|---|---|---|---|---|
| Lean team + QA | 5–6 months | $64K–$72K | $320K–$432K | $375K |
| Faster team + QARec | 3.5–4.5 months | $92K–$96K | $322K–$432K | $400K–$425K |
Recommendation
We recommend the faster team with QA at approximately $400K CAD. It buys momentum and quicker validation, and — importantly — it is not dramatically more expensive than the lean team, because the higher monthly burn is offset by a compressed schedule: the same scope is delivered in less calendar time, so the total lands in a comparable range while the product reaches a testable state sooner.
Best case
DALP cleanly handles most auth, identity, token and claim flows, keeping the work close to the calibrated baseline.
Risk case
DALP gaps require backend wrappers, custom permissions, or workaround flows, which would push effort toward the upper end of the ranges.
These ranges are pending technical validation of the story-point calibration; the next step converts them into a committed schedule.
MVP first; Phase 1 & 2 as extensions
Roadmap
88 stories · 353 pts
Phase 0 — MVP
The foundational build: the Investor app, the Issuer/Admin app, the Novark backend, and the DALP integration delivered as a working platform. This is the only phase covered by the quote.
33 stories · 134 pts
Phase 1 — extension
Deepening the cap table, opportunities, transactions and documents. Scoped here for planning, not included in the Phase 0 quote.
9 stories · 36 pts
Phase 2 — extension
Withdrawals, fundraising and secondary-market flows. Scoped here for planning, not included in the Phase 0 quote.
All phases combined (P0 + P1 + P2, ~523 points): lean team 7–9 months, faster team 5–6 months. Lead with the MVP; treat Phase 1 and Phase 2 as roadmap extensions.
Our recommendation
On Settlement
Build on Settlement/DALP for the MVP and do not invest in a replacement now. The bulk of our effort goes into the Novark backend and integrations we own regardless, while Settlement removes the need to build authentication, identity, claims, and token/blockchain plumbing from scratch. Replacing Settlement should be treated as a separate strategic project, not part of the MVP.
Integration vs. replacement
Integrating with Settlement lets us ship the MVP on existing, proven auth/identity/claims/token infrastructure, whereas replacing it would mean rebuilding that entire stack before we deliver any user-facing value.
Lock-in assessment
The dependency on Settlement is concentrated in auth, identity, claims, and token operations — a bounded, well-understood surface rather than a pervasive coupling, which keeps the lock-in manageable and explicit.
Architectural flexibility
We keep DALP behind a thin integration/adapter layer and retain ownership of the PII database and application logic, so the rest of the system depends on our interfaces rather than on DALP directly.
Migration as a separate project
Replacing Settlement should be a distinct strategic initiative scoped on its own terms and timeline — not folded into the MVP — and the adapter boundary ensures any future migration stays contained.
What we'd resolve before locking the schedule
Risks & Open Questions
Risks & mitigations
Story-point calibration is unvalidated
Our estimates rest on story-point assumptions we have not yet validated, so the timeline is presented as a range until we calibrate against real team velocity.
DALP capability gaps
Gaps in DALP may force backend wrappers, custom permission models, or workaround flows — mitigated by isolating DALP behind the adapter layer so any compensating logic lives in one place.
Settlement lock-in
Dependence on Settlement for auth, identity, claims, and token operations is a real concentration risk — mitigated by the adapter boundary that confines that dependency to a single, replaceable seam.
Third-party readiness
Delivery depends on the readiness and credentials of SumSub, Twilio, and FusionAuth — mitigated by securing sandbox access and API credentials early so integration risk surfaces before the build.
Compliance scope
The scope of encrypted PII and GDPR obligations is not yet fully defined — mitigated by confirming compliance expectations up front so data handling is designed to requirements rather than retrofitted.
Open questions / access needed
- Final Figma access
- DALP / Settlement sandbox access
- API credentials and documentation for SumSub, FusionAuth, and Twilio
- Hosting / cloud environment confirmation
- Whether Webisoft owns backend architecture decisions
- Admin permissions and who can issue claims
- Compliance expectations for encrypted PII / GDPR
Next Steps
Three steps to turn this into a committed plan.
Share access and credentials
Share Figma, DALP/Settlement sandbox access, and third-party credentials (SumSub, FusionAuth, Twilio) so integration work can begin.
Confirm the team option
Confirm the preferred team option — lean or faster — so staffing and scope are locked.
Validate story-point calibration
Validate the story-point calibration against real velocity to convert the timeline range into a committed schedule.
Direct contact: william@webisoft.com
Webisoft · Montreal, QC · webisoft.com
Confidential — Novark · Settlement / DALP Integration Platform