Two portraits. One conversation.
Most couple quizzes hand you a score and call it insight. Wrenlight does something quieter and more useful: a discussion framework woven from everything each of you has learned about yourself here — without either of you having to hand over a single test result.
The idea
You've each taken tests here — how you fight, how care lands, what recharges you, how you repair. Each result is private, and stays private. But between two portraits there's a third thing: the pattern between you. Where you're naturally aligned. Where you differ in ways that quietly do work for the relationship. And where you differ in ways that keep producing the same Tuesday-night argument.
Wrenlight for Couples reads both portraits and writes about that third thing only. Not "she's an Avoider," not "he scored 71 on closeness" — but "one of you needs space before words come, and one of you needs words before space feels safe. Here's what to do with that."
How it will work
Each of you builds your own portrait, on your own account, in your own time. Nothing about this step is shared.
One of you sends a couple invite; the other accepts. Double opt-in, every time a framework is generated. Either of you can revoke it, and the framework dissolves.
The synthesis reads both portraits and writes only about the pattern between you — derived insights, never scores, types, or answers.
You get a discussion framework: dos & don'ts, accommodations each of you can make, and conversation starters. It's an agenda, not a verdict.
The privacy model
This only works if neither of you has to trade away your private results to get the shared picture. So the boundary is structural, not a setting:
What the framework contains
- Patterns between you — alignment, complement, friction
- Dos & don'ts, written symmetrically — both of you always get an accommodation
- Conversation starters drawn from your actual dynamics
- How the picture deepens as more tests are woven in
What stays yours alone
- Your individual test results and archetype names
- Your dimension scores — all of them
- Which test (or answer) produced any given insight
- Anything you took before — or after — the couple link
One more rule, and it's the most important one: every friction insight is written symmetrically. There is no version of this framework that says one of you is the problem. If a pattern needs an accommodation, both of you get one.
See what your tests would unlock
The framework is built from the tests you've both taken. Check off tests below as if you and your partner had each done them, and watch the report take shape. The example insights are from a fictional couple — Maya & Sam.
Build a sample framework
0 of 24 testsAssume both of you take each test you check. Two tests in a theme open that chapter; more tests deepen it.
A page from a finished framework
Here's the texture of the real thing — one aligned pattern, one complementary one, one friction pattern, fully written. Notice what's absent: no types, no scores, no winner.
Where you meet, where you trade, where you grind
Built from 11 tests each. Seven of nine chapters shown — same density and tone as your own would have.
Both repair fast and forgive faster
Neither is a grudge-keeper. After a rupture, both reach for repair within hours — not days — and neither needs the other to grovel first. The behavioral signature: a text within the same evening, an apology that names the specific thing rather than a vague "sorry for earlier," and a return to ordinary contact (a question about dinner, a shared joke) as the closing move. This combination is rarer than it feels from the inside — most couples have one fast repairer and one slow one, and that asymmetry produces some of the heaviest long-term grievance work in the literature.
Watch-out: fast repair can paper over patterns that needed a longer look. Once a season, the framework suggests asking together: "is there anything we keep apologizing for instead of changing?" — and giving each other 24 hours to answer privately before comparing notes.
Same internal clock on decisions
When something needs deciding — a flight to book, a contractor to choose, whether to say yes to the dinner — Maya and Sam reach for the same speed. Both like to sit with it a day or two; neither flips coins, neither needs three weeks. This shared velocity removes a kind of friction most couples don't realize is friction until it's gone: the meta-argument about why the other person is so slow, or so impulsive. They get to argue the merits of the decision itself, which is usually shorter and more useful.
Watch-out: shared velocity can lock in a shared blind spot. Once a year, ask each other: "what's a decision we made fast that we now wish we'd sat with longer?" Or vice versa. Calibration is cheaper than regret.
Sam plans; Maya makes it a story
Sam builds the scaffolding — bookings, routes, the reservation that saved the evening, the early-Sunday departure that avoided the traffic. Maya supplies the appetite — the detour to the bookshop they almost skipped, the conversation with the stranger at the bar, the reason there's a story to tell at all. Each has probably read the other as "rigid" or "flaky" at some point.
The framework's read: they are each other's missing half of the same competence. This pattern repeats well past holidays — into dinner parties (Sam plates; Maya sets the table mood), weekend mornings (Sam makes the coffee; Maya makes the plan to walk somewhere new), big household projects (Sam tracks the budget; Maya picks the materials that make the room feel like theirs). The accommodation is one sentence each, occasionally and specifically: thank the other for the half you don't do, by name.
One social glue, one quiet refuge
Maya recharges through people — she's the one who keeps the group chats alive, suggests the dinner with friends-of-friends, calls the parents on a Sunday afternoon. Sam recharges in stillness — long solo runs, an evening with a novel, the deliberate week without plans. Together, the household has both: real social ties that wouldn't survive Sam alone, and a real quiet refuge that wouldn't survive Maya alone.
Watch-out: each partner can quietly resent the cost of the other's recovery mode — Sam can feel ambushed by the dinner Maya said yes to; Maya can feel abandoned by the Saturday Sam spent reading. The accommodation is naming each other's recovery as work, not absence: when Sam takes the solo run, he's protecting the household's silence budget; when Maya takes the call, she's protecting the household's belonging budget. Both are real labor.
Heat meets distance
When conflict sparks, Maya moves toward it — voice rises, words come fast, engagement feels like caring. Sam goes quiet and needs to leave the room to find his actual position. Each reads the other's move as the threat: Maya reads Sam's retreat as abandonment; Sam reads Maya's pursuit as attack. Neither read is true. Pursuer-distancer is one of the most studied dynamics in couple research (Gottman's "demand-withdraw," Johnson's EFT); the through-line of the work is that it doesn't stabilize on its own — it requires an agreed protocol, and the protocol has to give each partner half.
Maya doesLet the pause happen once Sam names a return time. Use the gap to write down the single sentence you most want him to hear — it will survive the hour and land cleaner than the ten raw ones would.
Maya doesn'tFollow Sam into the next room, text mid-pause, or treat the pause itself as a verdict on the relationship.
Sam doesCall the pause WITH a return time before you leave the room — "I need an hour, I'm back at 9" is a complete sentence — and keep it within ten minutes.
Sam doesn'tLet silence stretch past the agreed time, or use the pause to settle the thinking alone. The return conversation has to actually happen, and Maya has to be in it.
Care lands in different languages
Maya's primary receiver-language is words — verbal affirmation, "I'm proud of you," the specific compliment about the thing she worked on. Sam's primary receiver-language is acts — the coffee already made, the broken handle quietly fixed, the calendar pre-cleared for her busy week. Each is generous; each gives mostly in their own language. So Maya tells Sam how much she appreciates him, often — and Sam fixes the broken handle and asks no thanks. Each gives genuinely, and each often feels under-cared-for, because the signal isn't reaching the channel that registers.
Maya doesPick one concrete act per week aimed at Sam — clear his Monday morning, pre-pack the weekend bag, handle the appointment he keeps putting off. The point is the action, not the announcement.
Maya doesn'tTranslate the act into words ("I did this for you because…"). The acts language IS the channel; narrating it routes it back through Maya's channel and dilutes the signal.
Sam doesPick one specific verbal affirmation per week — one sentence, named to a thing she actually did, said out loud or in a text. "The way you handled that presentation prep on Tuesday — that was you at your best."
Sam doesn'tSubstitute a quiet act instead because it feels more comfortable. The discomfort of speaking it IS the work; the act version isn't a substitute, it's the channel she already isn't receiving from.
Money: one zooms in, one zooms out
Sam reads the credit card statement line-by-line and notices the $14 charge that didn't make sense. Maya tracks the long arc — savings rate, whether the next year's trajectory makes sense, whether the house decision still works at a higher rate. Each reads the other's mode as a deficiency: Sam can feel like Maya is careless with details; Maya can feel like Sam is missing the forest for one transaction. Both reads are wrong; the household actually needs both modes, but it needs them in separate domains, not in the same conversation.
Sam doesOwn the monthly review — categories, anomalies, the one chart that says whether the month behaved. Report the headline to Maya in two sentences at the end of the month.
Sam doesn'tOpen line-item conversations mid-week. The mode is "month-end report," not "running commentary" — running commentary is where Maya's attention budget collapses.
Maya doesOwn the quarterly horizon — savings rate, big decisions on deck, the trajectory question. Bring one chart and one question to a 30-minute meeting on the first weekend of each quarter.
Maya doesn'tOverride Sam's monthly review with the trajectory question. The two layers don't share a meeting; the structure is what lets both modes do their actual work.
Every insight above is derived from instrument data — and Maya never sees Sam's conflict-style result; Sam never learns Maya's attachment reading. The framework speaks only in patterns-between — and every friction pattern carries an accommodation for each name, never just one. In your framework, your names sit where theirs do.
The methodology, briefly
The same instruments that power your Portrait power this — scenario-based questions, three measurements per trait, honest valence handling. The couple synthesis adds three rules of its own:
Every cross-portrait finding is classified as aligned, complementary, or friction-prone. Nothing is ever summed into a number. Compatibility scores read as prognosis — and couples don't need a prognosis, they need a protocol.
Friction insights must name an accommodation for each partner or they don't ship. The framework is structurally incapable of taking sides.
Chapters only open when enough overlapping tests support them — a minimum of two per theme, eight or more for the full framework. Thin data gets a thin claim or none, never filler.
Ready when you are. The framework gets richer the more tests both of you have taken — the synthesis only writes a chapter when there's real data behind it. The single best preparation: keep building your own portrait, then send the invite.