Case studiesResidential real estate

Mark Spain: connecting sales, content and partner offers

Mark Spain Real Estate needed its sales, partner-offer and publishing systems to work together. Paulo Cardoso, through Upstart13, built the backend connections and supported the content and infrastructure migration.

Business
Mark Spain Real Estate
Sector
Residential real estate
Scope
Backend, content and partner integrations
Contributor
Paulo Cardoso through Upstart13
Editorial illustration: architectural house models joined by one orange threshold
AI-generated editorial illustration of the project’s domain.

An appointment needed a reliable route to a partner offer.

The website, Salesforce and Homeward each held part of the property-sales workflow. An appointment created in one system needed to become the right offer request in another, with fields and state carried across the boundary.

Publishing was also moving from WordPress to Strapi. The project therefore combined business-process integration with content migration and the AWS network configuration required by the partner service.

Connect the systems and rehearse the migration.

Node.js services on AWS Lambda and API Gateway connected Salesforce, Homeward and the publishing stack. The work mapped the appointment-to-offer flow with the partner teams, so each service received the information it expected.

Content moved to Strapi v4 and media to Amazon S3. Staging simulated the production infrastructure before cutover. Private subnets, a NAT Gateway and an Elastic IP supplied the fixed outbound address required for partner allowlisting; CloudWatch and WAF supported the surrounding infrastructure.

What the workflow includes

  • Map sales appointments into partner offer requests.
  • Move WordPress content and media to Strapi and S3.
  • Rehearse content and infrastructure changes in staging.
  • Meet partner access requirements with a fixed outbound IP.

Project details

Diagram showing a serverless AWS integration layer connecting Salesforce, Homeward, Strapi, the Mark Spain website and internal services

Project materials showing the workflows and interfaces described in this case.

Sales and publishing gained a defined integration layer.

The delivery connected the sales workflow and the publishing migration through a defined backend. Partner networking requirements were handled alongside application behavior, making the integration deployable in its intended environment.

What this means for the technology owner.

Taking over an integration means understanding both the API and the agreements around it. Field mappings, partner allowlists, deployment settings and migration steps are part of the operating record. Losing that context can break a business process even when the application code remains available.

How to hand over software to a new team →

Node.jsAWS LambdaAPI GatewaySalesforceStrapiCloudWatchVPCAWS WAF

Project contribution: Paulo Cardoso through Upstart13. The scope described above identifies the work behind this case.

Editorial review: Ego Eimi · Updated September 6, 2026 · About the team

Your technology

Start with the business

Your business depends on it.

Tell us which system matters, what has changed and who controls it. We will define a reviewable next step. Read Foundation and the commitments and evidence.