Lists go stale when you sell to architects
How old is the list you are about to email? Here is how people who sell to architects fix it.
How old is the list you are about to email?
Businesses move, close or change their website, and a list that was accurate last year slowly decays. Bought lists are often stale before you receive them.
It hits harder when you sell to architects. Architecture practices are often small studios led by one or two directors, with larger firms organised by sector. They specify materials and products on projects, so suppliers want to be known to them long before a build starts.
Stale data means bounces and wasted effort on companies that no longer exist. It also hurts your sender reputation.
You choose the source, so you control freshness.
In Riftjaw you supply the source yourself, so you decide how fresh it is. Import a new version of a list and duplicates against your database are flagged, so only new companies are added. Records that are no longer relevant can be archived, and every record shows the date it came in.
- Fields that fit architects, such as sectors
- Email prefixes that fit, like info@, studio@, hello@ and office@
- Status, tags and a segment on every record
How to fix it in Riftjaw
- Collect a fresh list. Export a current list from the directory or source you trust.
- Import against your database. Duplicates are flagged and only new companies are added.
- Archive the old. Move records that no longer fit to archived.
Other walls when prospecting architects
Architects receive many supplier mails and ignore generic ones.
Placeholders and segments per sector let you send a relevant message instead of one blast.
Small studios often have only a studio@ address.
Add studio@ as your own prefix in email from domain.
Specification takes months, so follow-ups get lost.
Tags and notes on each contact keep the thread, and you can filter on them months later.
Fields worth recording for architects
Add these as fields in your lead file. Any column in your import can become a field.
| Field | Why it helps |
|---|---|
| Company name | The key field. Duplicates are checked on it or on the website. |
| Website | Needed to derive an email when the export has none. |
| Sectors | Residential, commercial or public work each specify different products. |
| Architects | Studio size shows project scale. |
| Software | The design package they use matters for any software offer or file exchange. |
| Recent project | A named project gives you a concrete, relevant opening. |
| Director | The person who approves suppliers and specifications. |
Questions people ask
Add a field or tags for sectors such as residential or commercial. Save a filter per sector and write a campaign for each.
Public planning records often name the agent or architect. You collect those names yourself, save them as a CSV and import them. Riftjaw does not crawl those sites for you.
If your file has an email column, that wins. If it only has websites, tick the prefixes you want, such as info@, studio@, hello@ and office@, and Riftjaw derives addresses from each domain. Derived addresses are good guesses, not verified, so start with small batches.
Yes. The Free plan runs the whole pipeline on one list with small campaigns, and you do not need a credit card. Move to Pro when you want more lists, segments and bigger campaigns.
Build the list in a city
Build a database you own
Create your account, import your first list and see it turn into records you can work.
No credit card · cancel any time · your data stays yours