Delivery plan
Phases
What gets built, in which order, and what we need from you at each step. 5 phases over 5 months, with a demo at the end of every sprint.
Dates assume kickoff on 1 November 2026; every phase moves with the actual start.
- 2-week sprintsA fixed rhythm: each sprint ends with something you can use.
- A demo every sprintWe show the working product, not slides.
- A test environment from week 2You can click through what is built, before it goes live.
- Weekly statusA short written update: done, next, and what we are waiting for.
Phase by phase
Phase 1 · Month 1 · Weeks 1 to 5
Infrastructure, environments, connecting the first provider (IBI)
What gets built
- Dedicated server with a fixed IP and separate dev, test and production environments
- FIX 4.3 connection to IBI: logon, heartbeat, automatic reconnect, sequence reset
- Rate subscriptions per pair with up to 5 depth levels; a pair marked not tradable drops out
- Monitoring and an alert when the IBI connection drops
What you will see
The FIX connection log: logon, subscriptions and live sample rates coming in, and a pair suspended when IBI marks it not tradable.
What we need from Shilan
- IBI credentials and access to IBI's test environment
- Decision: the list of currency pairs to open (the working assumption is the major currencies against the shekel and the dollar)
Phase 2 · Month 2 · Weeks 5 to 9
Core, API, spread engine, Kashcash API
What gets built
- One database for clients, trades and collateral, and the API layer every channel uses
- Spread engine: per channel, partner, client group or single client, on top of the IBI base rate
- Collateral and trading limit checked on every trade (10% collateral)
- Kashcash rates API: fixed rate per time window, its own spread, a dedicated key, a rate limit, a closed-market flag
What you will see
A real request to the rates API with a Kashcash key, answered with its own spread; a spread change taking effect at once.
What we need from Shilan
- Decision: the spread per pair for Kashcash
- Decision: how long a rate stays fixed for Kashcash and locked for a site client
- Decision: the margin threshold (when to alert, when to close a position)
Phase 3 · Months 2 to 3 · Weeks 5 to 13
Back office and customer management
What gets built
- Main dashboard: turnover, trades, open exposure, collateral
- Client approval queue with documents, guarantee and an approve or reject reason
- Dealer hedging queue, one task per trade
- Matching incoming bank transfers, spread management, reports with Excel export, roles
What you will see
The back office on the test environment: approving a test client, a hedging task appearing for a test trade, changing a spread.
What we need from Shilan
- The staff who will use it, and their roles: admin, dealer, client approver, viewer
- Decision: which banks and what format the transfer details arrive in
- IBI's trading API document, if automatic hedging is wanted later
Phase 4 · Months 3 to 4 · Weeks 9 to 18
Shilan Trade app, sign-up and trading
What gets built
- Onboarding: account and SMS code, ID upload, digital guarantee, collateral deposit, verification by Shilan
- Trade screen: pair, side and amount, rate locked for 10 seconds, limit checked
- Personal area, notifications, full Hebrew right to left on mobile and desktop
What you will see
A test client going from sign-up to a first trade on the site, and the same client appearing in the back office queue.
What we need from Shilan
- The text of the guarantee for signing
- Shilan's bank account details for collateral deposits
- Decision: when to move from manual to digital client verification, and which provider
Phase 5 · Months 4 to 5 · Weeks 13 to 22
Partner programme, first partner live
What gets built
- Adding a partner in the back office: details, licence, contact, commercial terms
- Branding: logo, colours and the partner's own domain; the partner's spread and pairs
- A restricted partner back office and the first partner's site going live
What you will see
The first partner's own branded site, live on its domain, with its clients trading at its spread through Shilan Trade.
What we need from Shilan
- Decision: whether partners trade under Shilan's licence or their own, and each side's responsibility
- Decision: the revenue model with partners (set-up fee, monthly fee, spread share)
- The first partner's logo, colours and domain
The plan depends on IBI's technical team being available and on receiving their test environment. Weeks count from kickoff.