Field guide
Notes from connecting organisations
Practical answers for operations, finance and IT leads planning a portal or integration, whoever ends up building it.

Planning
Before you start
Which flow should go first?
The one that is painful, frequent and owned by someone willing to make decisions. Avoid starting with the most politically complex flow.
Do we need a data warehouse?
Not to start. Many organisations need a few reliable connections and one reconciled dataset long before they need a warehouse.
What should we ask vendors?
Whether their product has a documented API, what it costs to use, its rate limits, and whether test environments are available.
Operating
While it runs
Who should own exceptions?
A named person in the business team that owns the data, with a deputy. Technical teams fix causes; business teams decide what a record should say.
How do we know it is working?
Ask for counts: records in, out and rejected per run, visible without logging into a server.
What about vendor updates?
Subscribe to their change notices and include interface checks in your support arrangement.
Money
Budgeting
What drives cost?
Number of systems, quality of their interfaces, volume of exceptions and how many user roles a portal has. Screens matter less than people expect.
What does it cost to run?
Usually modest hosting and monitoring, plus any per-call API fees. We estimate running costs before you commit.
Fixed price or not?
Fixed for well-mapped slices; capped time and materials for discovery-heavy work. The connection map tells you which.