HOUSE 813 | NOTES ON BRANDING / 11 | TECHNICAL SOLUTIONS

Technical solutions: defining an integration or automation project

Technical solutions: defining an integration or automation project

"Connect these two tools" sounds like a small brief. It can hide several decisions: which information should move, when it should move, who is allowed to see it and what should happen when something fails.

"Connect these two tools" sounds like a small brief. It can hide several decisions: which information should move, when it should move, who is allowed to see it and what should happen when something fails.


Illustrated form and project record connected through a field map and an approval checkpoint.

A useful technical brief starts with the work, not the connector. Describe the process you want to improve, then define the smallest reliable change that would make it easier to run.

Describe the current process in plain language

Write down what starts the work, what happens next and who handles each step. Include the tools, documents and manual checks involved. A simple sequence is more useful than a list of software names.

For example, a business might want an approved enquiry to become a record in its project system. That is a hypothetical workflow, not a claim about an existing House813 integration. The brief still needs to say what makes an enquiry approved, which fields belong in the record and who checks the result.

Mark where time is being lost or mistakes occur. Do not automate a step simply because it is manual. Some steps are decisions that should remain with a person, especially when money, access or external communication is involved.

Define the information and its source

List the fields that need to move and explain what each means. Names, dates and status labels can look similar across tools while describing different things.

Choose the system that holds the authoritative version of each important fact. If someone edits a record in both places, decide which change wins or whether the conflict needs review. Include how existing records will be matched and how duplicates should be handled.

Use sample data that is safe to share when discussing the design. Do not place customer records, passwords or access keys in an open brief. Agree how necessary access will be provided through an appropriate secure route.

Check the actual connection options

Ask what each tool supports in the account and plan you use. A built-in connector, an API or a scheduled export may offer different fields and limitations. A tool having an API does not prove that it exposes the specific action your workflow needs.

Confirm authentication requirements, permissions, usage limits and any paid dependencies before treating the connection as straightforward. Keep a distinction between a documented capability and a successful test in the actual environment.

Decide how quickly information needs to arrive. A periodic sync and an event-triggered update solve different timing problems. Avoid requesting instant updates if the business process does not need them.

Specify failure behaviour before the happy path is finished

Define what happens if a service is unavailable, a field is missing or the same event arrives twice. Decide which failures can be retried and which need someone to inspect them.

Stripe's webhook documentation is a useful example: it describes retries, duplicate events and delivery that is not guaranteed to follow the order events were generated. Those are Stripe-specific behaviours, not universal rules for every connector. The broader planning lesson is to check the chosen system's delivery rules rather than assuming each event arrives once and in order.

Agree how the team will see a failure, who owns it and how an incomplete item can be recovered. An automation that silently stops creates a new manual problem instead of removing one.

Write acceptance checks the business can understand

Describe what a successful result looks like using concrete test cases. Include a normal item, missing information, a duplicate, a changed record and a temporary failure where relevant.

For each case, state the expected result and who can approve it. Check that the wrong person cannot see restricted information and that the automation cannot make an unapproved external commitment.

Use a test environment or an agreed controlled trial where possible. Record what was actually tested and what remains unverified. A successful demonstration with one sample is not proof that every live case is covered.


Hypothetical enquiry-to-record workflow with missing-data review and duplicate handling.

Plan ownership after launch

Name the owner of the accounts, ongoing costs, monitoring and future changes. Document the important settings and a way to pause the workflow safely. Agree what happens when a tool changes its API or a person loses access.

Start with a bounded process, clear inputs and a testable outcome. That makes scope easier to discuss and gives the business a way to judge whether the work is ready.

Explore House813 and share the process, tools and handoffs you want to improve. The first useful deliverable is a clear problem, not a promise that every tool can connect to everything else.

Next: Which House813 service does your business need first? →

HOUSE 813 / NOTES ON BRANDING 11

Technical solutions