Engagement
Schema and contract check
Portals lie politely. A field labelled ‘account number’ may be a legacy code. An export column may use a different date than the screen. This check is for teams who have been surprised by that gap.
From RM 9,600 · 8–12 working days
You provide a bounded set of contracts — OpenAPI snippets, sample payloads, CSV exports, or admin documentation. We read them against the customer screens, not against an architecture diagram.
The report is useful to engineers and to operations. It names the field, the screen, and the consequence if they continue to disagree.
We do not rewrite your APIs. We show where the portal and the contract have already drifted.
What is in the pack
- Comparison of key screens, form posts, and agreed export or API samples
- A mismatch register: label, stored value, downstream use
- Notes on optional fields that are silently required later
- Recommended contract tests your team can keep running
Fees are informational. We invoice after a scoping call. There is no payment form on this site.
