Schools
“Results computed by hand every term, parents owing fees, and report cards chased on WhatsApp.”
What we build: Results and report cards, fee tracking with reminders, parent access, attendance and CBT exams.
See the school demo →FASS Custom Builds
A custom build is software made around how your school, estate or business runs: results and fees, rent and plots, payroll, or a client portal. It is quoted after a free scoping conversation and paid in stages: 50% on signing, 25% at the first working demo, 25% on approval and handover.
Fadiya Software Solutions Ltd · Abuja, Nigeria · Written scope before build · Phased delivery where useful
A useful starting question
That is usually a better brief than “we need an app.” Bring the current process, the people involved, and the records that matter. We can work forward from there.
Who custom builds are for
Most of the people we build for would never call themselves an enterprise. A school, an estate, a ten-person firm or a church committee qualifies as soon as the work depends on records, payments, approvals or more than one person needing to see the same thing.
“Results computed by hand every term, parents owing fees, and report cards chased on WhatsApp.”
What we build: Results and report cards, fee tracking with reminders, parent access, attendance and CBT exams.
See the school demo →“Who has paid, who is owing, and no receipt or record to settle the argument.”
What we build: Rent and service-charge records, numbered receipts, tenant and resident statements, and repair requests.
See the property demo →“Payroll in a spreadsheet, PAYE worked out by hand, and payslips sent one by one.”
What we build: Payroll with PAYE and pension, payslips, leave and attendance, with approvals on record.
See the HR & payroll demo →“Clients keep calling for updates, and their documents live in WhatsApp and email threads.”
What we build: A secure client portal with job status, shared documents and messages in one place.
See the client portal demo →“Requests, approvals and stock spread across five WhatsApp chats and a notebook.”
What we build: One operations desk for requests, approvals, stock and reports that managers can trust.
See the operations demo →“Members, dues and donations tracked in notebooks, with no clear report for the committee.”
What we build: Member records, dues and giving with receipts, and simple reports for leaders and donors.
Describe what you track today →Not sure which side you are on? If customers only need to find you and contact you, a website package is enough. If your staff, parents, tenants or clients need to log in, see their own records, pay, or follow a request, it is a custom build. Tell us what happens today and we will point you to the smaller option when it fits.
Start from the bottleneck
You do not need to know the product category in advance. These are common signs that a portal, operations system, or role-aware application may be more appropriate than another spreadsheet or public website.
01
Requests move through chats and calls, so nobody has one reliable view of what is pending, approved, rejected, or complete.
02
Staff copy information between spreadsheets, forms, email threads, and separate tools just to move one process forward.
03
Clients, staff, managers, agents, teachers, parents, or executives need access to the same operation without seeing the same things.
04
Your team spends time answering questions that a secure client or member portal could make visible on demand.
05
Managers only know what happened after someone reconciles files, messages, or departmental records manually.
06
A generic ERP or SaaS product introduces workarounds because the organisation's real workflow does not fit the product's assumptions.
Working reference systems
These are FASS-built reference implementations using fictional organisations and demo data. They are not client case studies. Use them to inspect the interaction patterns, role boundaries, and workflow depth we can discuss for a real organisation.
Working reference
Fictional dataAdvisory firms & B2B services
Advisory and B2B firms get a branded client lane — document sharing, messaging, and role-based access — without enterprise complexity or six-month timelines.
Working reference
Fictional dataOperations teams & logistics
Operations teams get request workflows, manager approvals, and exportable reports — custom internal tooling without buying a full vertical ERP you will never fully use.
Working reference
Fictional dataHR teams & growing employers
Nigerian employers run multi-branch payroll, payslips, leave, and attendance from one platform — with HR Admin, Manager, and Employee views that match real org structures.
Working reference
Fictional dataSchools & education groups
Nigerian schools run nursery, primary, and secondary workflows from one platform — CBT mocks, timetables, parent portals, and teacher dashboards built for local exam patterns.
Working reference
Fictional dataProperty developers & estate managers
Property developers manage estates, plots, payments, and agent referrals from one ERP — with Staff, Client, and Agent portals scoped to each development.
Working reference
Fictional dataGroups & multi-division companies
Multi-division companies unlock CRM, Finance, and HR modules by phase — each gated until the next milestone, matching how FASS scopes modular build engagements.
How custom builds are scoped
01
Start with the people, records, hand-offs, approvals, exceptions, and bottlenecks. A finished feature list is not required.
02
We separate the first operational problem worth solving from future modules so the project can produce value before it becomes large.
03
A first conversation is free. Where the scope needs deeper analysis, paid discovery produces a written requirements and architecture summary before the build commitment.
04
Roles, workflows, integrations, migration, and acceptance criteria are written into the scope and reviewed at defined delivery points.
When a deeper scope is needed
Paid scoping work credited toward the build if you sign within 30 days. You receive a requirements workshop, architecture outline, effort/timeline estimate, risk notes, and a written summary. The fee is credited toward the build when the stated credit conditions are met.
Common starting scopes
A custom build is not a website package, so there is no fixed price list. These are common starting shapes to orient the conversation. The quote depends on roles, data, integrations, migration, security, reporting, and the number of operational boundaries the system has to carry. The first conversation and initial quote are free, and you get the scope and price in writing before any build starts.
Common starting scope
Quoted after scoping
Typical timeline: 5–7 weeks
Secure client or staff portal with role-based access.
Common starting scope
Quoted after scoping
Typical timeline: 8–10 weeks
Custom internal software for a defined operational workflow.
Common starting scope
Quoted after scoping
Typical timeline: 12–16 weeks
A property, HR, school, or similar operational system shaped from working FASS reference implementations and the organisation's actual requirements.
Common starting scope
Quoted after scoping
Typical timeline: Phased (20–32+ weeks)
A multi-module platform scoped and delivered in agreed phases.
Start the custom build conversation
Tell us what happens today, who touches the process, what records are involved, and where visibility or control breaks down. The first conversation and initial quote are free.