Based on our discussion on February 20, 2026, we've structured two distinct engagement tracks that reflect a critical distinction: one initiative has clear requirements and can move directly to scoping and build; the other is complex and ambiguous, requiring design thinking discovery before anything can be estimated or built.
| Track | Initiative | Approach | Timeline | Investment |
|---|---|---|---|---|
| Model 1 | Giving Platform | Scope → Estimate → Build | 8–10 weeks | SGD 40K–80K |
| Model 2 | Pastoral Care System | Discovery → Scope → Build | Discovery: 5–6 wks Build: TBD post-discovery | Discovery: SGD 30K–40K Build: SGD 120K–250K+ |
| 💡 Both tracks can run in parallel. Model 1 delivers a live product while Model 2 discovery is still underway. | ||||
Why no discovery sprint? NCC confirmed the giving platform has clear, well-understood requirements. It's a digital channel for congregational giving with backend analytics and donor tracking. The problem is defined, the solution is known. Discovery would add time without adding value here. We scope it, estimate it, and build it.
| Option | How It Works | Best For |
|---|---|---|
| 🔒 Fixed Cost | We sit down with you, lock the scope, then give a fixed-price quote. No surprises on cost — you know exactly what you're paying before we start. | Clear, well-defined requirements |
| 📅 Man-Days | We quote a low-to-high estimate upfront. Billing is SGD 420/person/day. Scope can grow or shrink as the work progresses. Weekly timesheets, full visibility. | Scope that may evolve or expand |
| Line Item | What It Covers | Low–High |
|---|---|---|
| Onsite sessions (~2.5 days, team of 3) | Flights, hotel, meals, daily rates | ~SGD 9,810 |
| Design & prototype | Remote design work, 1–2 weeks | SGD 6,000–10,000 |
| Engineering: frontend | Web + mobile giving interface | SGD 8,000–18,000 |
| Engineering: backend | Donor DB, analytics, admin panel, APIs | SGD 8,000–20,000 |
| QA, deployment, documentation | Testing, staging, go-live, handoff docs | SGD 4,000–8,000 |
| Total Estimate | SGD 36K–66K | |
Fixed Cost: range narrows to a single number after scope session (Day 1). Man-Days: low-to-high estimate provided upfront, billed at actuals weekly.
* All figures shown are indicative estimates only. A formal proposal with final, confirmed pricing will be issued on engagement.
** Post-development support and maintenance arrangements will be discussed separately.
Why discovery first? Nine ministry functions. No unified data model. Volunteers, pastoral staff, and technology stakeholders all with different workflows and needs. The build cannot be scoped until we understand the problem deeply. What exists today, where the breakdowns are, what "good" looks like, and whether to buy, configure, or build. Skipping discovery here would mean scoping the wrong thing.
This is classic design thinking territory: understand → define → ideate → prototype → test. We run this as five structured sessions in Singapore. Two sprint formats are available: same five sessions, different scheduling and cost profile.
| Format | Schedule | Duration | Onsite Cost | |
|---|---|---|---|---|
| B1 Distributed Mondays | 1 session / week | 5 weeks | ≈ SGD 40,000 | Flexible |
| ⚡ B2 Compressed Sprint | Half-days, every other day | ~2 weeks | ≈ SGD 22,500 | Recommended saves ~SGD 13K |
B2 runs sessions Mon → Wed → Fri → Mon → Wed. Half-days (mornings only) protect NCC's schedule. Symph synthesises and preps each afternoon. Labor is the key cost driver half-day rates cut the facilitation cost from SGD 40,000 to SGD 30,000. Travel and accommodation are nearly identical for both formats.
Build investment (SGD 120K–250K+) is scoped and proposed separately, after Week 5 discovery is complete. You don't commit to the build until the brief is locked.
* All figures shown are indicative estimates only. A formal proposal with final, confirmed pricing will be issued on engagement.
** Post-development support and maintenance arrangements will be discussed separately.
Transparent line-by-line onsite computation for both models. The majority of both engagements is remote onsite is reserved for moments where physical presence matters: scope confirmation, discovery, and sign-off.
| Item | Rate | Notes |
|---|---|---|
| Team traveling | 3 people | Product Lead + Solutions Architect + Designer |
| Daily rate / person | SGD 420 / day | Per person, Singapore engagements |
| Flights (MNL → SG) | SGD 400 / person / trip | Economy round trip |
| Accommodation | SGD 180 / person / night | Business hotel, Singapore CBD |
| Meals & incidentals | SGD 80 / person / day | Per diem |
| Session | Labor | Travel & Hotel | Meals | Subtotal |
|---|---|---|---|---|
| Day 1 Scope Review (full day) | SGD 1,260 | SGD 1,740 | SGD 480 | SGD 3,480 |
| Day 2 Design Sign-off (half day) | SGD 630 | SGD 1,740 | SGD 480 | SGD 2,850 |
| Day 3 Go-Live Handoff (full day) | SGD 1,260 | SGD 1,740 | SGD 480 | SGD 3,480 |
| Total Onsite: Model 1 | ≈ SGD 9,810 | |||
| Item | B1 Distributed Mondays | B2 Compressed Sprint ⚡ |
|---|---|---|
| Facilitation labor | 3 × 5d × SGD 420 = SGD 6,300 | 3 × 5 half-days × SGD 210 = SGD 3,150 |
| Flights (1 return trip) | 3 × SGD 400 = SGD 1,200 | 3 × SGD 400 = SGD 1,200 |
| Accommodation | 3 × 10 nights × SGD 180 = SGD 5,400 | 3 × 10 nights × SGD 180 = SGD 5,400 |
| Meals | 3 × 10 days × SGD 80 = SGD 2,400 | 3 × 10 days × SGD 80 = SGD 2,400 |
| Total Onsite | ≈ SGD 40,000 | ≈ SGD 30,000 (saves ~SGD 10K) |
Labor is the dominant cost driver. Half-day sessions (B2) cut facilitation labor by 50%. Travel and accommodation are nearly identical. Both formats use one return trip with a ~10-night stay. Onsite cost is included within the discovery SOW total.
* All figures shown are indicative estimates only. A formal proposal with final, confirmed pricing will be issued on engagement.
** Post-development support and maintenance arrangements will be discussed separately.
Model 1 and Model 2 run in parallel without blocking each other. Model 1 ships a live product in 8–10 weeks. Model 2 runs its Monday discovery sessions during that same window. By the time Model 1 goes live, Model 2 has a locked brief and a build estimate ready to sign.
| Timing | Model 1: Giving Platform | Model 2: Pastoral Care |
|---|---|---|
| Now | 🟣 Scope Review 1 day onsite | |
| Week 1 | 🔵 Design & prototype begins | 🟣 W1 Current State Mapping |
| Week 2 | 🔵 Prototype review | 🟣 W2 Member Journey |
| Weeks 3–8 | 🔵 Build | 🟣 W3–W5 + 🔵 Prototype |
| Week 8–10 | 🟣 Go-live + handoff | 🔵 Build brief locked |
| Week 10+ | ✅ Live | 🔵 Build SOW issued → Build begins |
| # | Action | Owner |
|---|---|---|
| 1 | Confirm which models to proceed with | NCC |
| 2 | Lock Model 1 scope session date (onsite, 1 day) | NCC + Symph |
| 3 | Confirm first Model 2 session date | NCC + Symph |
| 4 | Identify stakeholders for ministries and leadership teams (Model 2) | NCC |
| 5 | Symph issues SOW(s) within 48 hrs | Symph |
By signing below, both parties agree to proceed with the engagement track(s) confirmed in writing and the terms in the Statement of Work to follow.
Every engagement starts from a different place. For what's already clear, we scope it, quote it, and build it. For what's complex and ambiguous, we discover it together first then build.
Siloed technology, coordination and data across nine ministry functions. No ability to focus on the members of the body to help them effectively.
Requirements are fuzzy or high-level. We can't scope or price a build yet. We run a design sprint together understand, define, ideate then prototype and quote the build.
Requirements are already clear. We sit down on the design and development scope, give you a quote, and work with you to build a POC or the full system.
Not every engagement needs a discovery sprint. Not every complex problem can skip one. We propose the model that fits the problem, not a one-size-fits-all process.
"Requirements are clear to you we sit down, scope it, give you a quote, and build it."
Design & development scope session → fixed-price quote → build POC or full system.
NCC's giving platform requirements are already well-defined. This is our standard engagement practice: we sit down with you on the scope, lock the design and development brief, give you a fixed-price quote, and work with you to build it whether that's a POC to test first or the full system straight away.
* All figures are indicative estimates. A formal proposal with final pricing will be sent on engagement.
** Post-development support and maintenance arrangements will be discussed separately.
"Requirements are high-level. We can't scope or price a build yet so we discover together first."
5 discovery sessions in Singapore → prototype → locked build brief → fixed-price build quote.
Nine ministry functions. No shared data model. Complex interdependencies across volunteers, pastoral staff, and technology stakeholders. We cannot responsibly scope or price a build for this without deep discovery first scoping the wrong thing here would cost far more than the sprint itself.
We run a design sprint with you in Singapore: structured half-day sessions where we map your current state, understand pain points, ideate solutions, and prototype. By the end, we have a locked build brief and that's what we price against.
Our quoted prices are all-in. Onsite sessions are a small part of both engagements the majority of the work is remote. Here's what each engagement covers.
* All figures are indicative estimates. A formal proposal with final pricing will be sent on engagement.
** Post-development support and maintenance arrangements will be discussed separately.
Model 1 and Model 2 don't block each other. By the time the Giving Platform goes live, the Pastoral Care discovery is done and the build brief is locked.
We bring the right people from Day 1 on both models, with a solutions architect on both to ensure the design delivers the value NCC wants.
Facilitates all onsite sessions, owns strategy and stakeholder alignment throughout
Day 1 on both models: platform selection, API design, buy vs. build, vendor coordination
Model 1: prototype. Model 2: journey mapping + prototype post-discovery
Remote delivery scoped and right-sized per phase and track
Five steps from this conversation to a signed engagement and dates in the calendar.
Model 1 only, Model 2 only, or both in parallel. Let us know.
One full day with NCC leadership and key stakeholders to confirm requirements and lock brief.
We run five sessions starting whenever NCC is ready. Ministry leads for 3, leadership team for 2. Adaptable to NCC's schedule.
Identify the stakeholders and the connections between them to ensure the right session planning.
Once models and dates are confirmed. Transparent scope, clear terms, no surprises.