We’re building Asym.
We’re Conrad and Blake.
Asym is a product for Christian missions organizations. Asymmetric.al is the nonprofit ministry behind it.
We don’t have customers yet. We do have a few organizations waiting to use it, a clear problem in front of us, and we’re building nonstop.
It is very early. Some parts are still ugly. Some parts are half wired. Some parts work well enough that you can already see where this is going.
The vision is simple.
Christian missions organizations should not need five disconnected tools, three spreadsheets, two CRMs, and a part time miracle worker just to keep donors, missionaries, gifts, receipts, websites, emails, reports, and workflows from falling apart.
That is not a small problem.
It eats hours every week from people who already carry a lot.
Mobilizers chase candidate paperwork. Finance teams reconcile gifts by hand. Missionaries wonder who gave, who stopped giving, and who needs a thank you. Member care teams try to keep track of who needs care before people fall through the cracks. Donors want a clean way to give, manage their gifts, and get receipts. Leaders want to know what is actually happening across the organization without asking someone to pull another report.
Most of the time, the people doing the work are not asking for something flashy.
They just want software that does not make their day harder.
That is what Asym is trying to become.
One Mission Control for missions and nonprofit operations.
We think Asym can become the operating system for missions organizations. That sounds big because it is. But it starts with ordinary things working the way they should.
Giving. CRM. Donor portal. Missionary portal. Receipts. Statements. Automations. Reports. Websites. Email. AI help where it is actually useful.
Not another dashboard for the sake of having a dashboard.
A working system that takes administrative weight off the people who are trying to serve.
We think missions technology is way behind where it should be.
Not because the work is unimportant.
Because the market has never served this kind of work very well.
The people doing some of the most meaningful work in the world often get stuck with the worst tools, because they are not an obvious software market and they do not have enterprise budgets.
That bothers us.
It bothers us that a missionary can raise support from fifty people and still not have a simple, beautiful way to know who gave, who needs care, and what to do next.
It bothers us that finance teams entrusted with donor money have to fight broken exports and manual reconciliation.
It bothers us that small missions teams often have to choose between expensive legacy software and patched together tools that constantly break.
We are not okay with that.
Asym exists because we believe small teams should be able to do more with less.
Not by working longer hours.
Not by adding more admin.
By giving them tools that quietly handle the boring parts, so they can stay focused on people, prayer, sending, care, discipleship, and the Gospel.
That is the purpose.
The product is early. The mission is not.
That is why we are looking for people who want to build with us before it is obvious.
People who can handle messy. People who care about craft, but do not need perfect conditions to start. People who can ship, learn, fix, and keep going.
People who understand that software can either drain a ministry team or give them time back.
We need builders who are comfortable owning real pieces of the system.
Not just having opinions about the work.
Owning it.
You might work on the donor portal one week, Stripe flows the next, Mission Control after that, and then a receipt PDF bug that absolutely has to work before year end giving.
This is not a polished big company job.
There is no giant team around each feature.
There is a lot to build, and every good decision matters.
We are building in public enough to learn fast, but carefully enough to protect the trust behind the work.
Financial data has to be right. People data has to be safe. Permissions have to hold. Receipts have to send. Reports have to match. AI has to respect boundaries.
The details matter because the mission matters.
The boring details matter because the mission matters. So we are starting with the ordinary work that has to be right.
A donor gives.
A receipt goes out.
A missionary sees the gift.
A staff member can find the donor.
Someone in finance can export the report.
A leader can understand what happened.
Then we make that smoother.
Then we make it faster.
Then we connect the next piece.
That is the work.
Come build the next piece.
A few good builders can change the daily work of a lot of missions teams.
That is the kind of team we want to build this around.
If you are looking for a clean, predictable, already figured out thing, this probably is not it.
If you want to help build the foundation for something that could serve thousands of missionaries and the organizations behind them, we should talk.
Asym is early.
We are building nonstop.
And we think this is worth giving ourselves to.
Conrad and Blake