Most of the teams we talk to already own most of the software they need. The tools are fine. The trouble is the gaps between them, and the person who fills those gaps with copy and paste.
So the first thing we do is look at what you have. If a product built for organizations like yours exists, we help you choose it. If the tools are right and only the connections are missing, we connect them. If neither works, we build, and what we build is in your repo and yours to keep.
We tell you which of the three we recommend, and why, in writing, before you spend on any of it. That is what discovery is for.
MalakMagnolia Development
P.S. When discovery says not to build, we say so and name the tool that fits. That is what happened with Rosie's House.
Manual work wastes time and introduces places where information can get lost or dropped. When you already know what works well for your business, automations and connections can be a real game changer for consistency and repeatability.
Illustrative stack and chores
8hand-offs done by hand
copy and pasteexport CSV weeklycheck for paymentsretype the bookingpaste into the reportforward the emailretype the totalscopy the names
Every hand-off now runs on its own.
Website forms to CRMBy hand: copy and paste.Connected with a native connector: new inquiry to CRM.
CRM to Email marketingBy hand: export CSV weekly.Connected with Make: contact and tags to list.
Accounting to CRMBy hand: check for payments.Connected with custom code: paid invoice to status.
Scheduling to CRMBy hand: retype the booking.Connected with a native connector: booking to contact note.
CRM to SpreadsheetBy hand: paste into the report.Connected with Make: records to report sheet.
Website forms to SpreadsheetBy hand: forward the email.No longer needed.
Accounting to SpreadsheetBy hand: retype the totals.No longer needed.
Scheduling to Email marketingBy hand: copy the names.No longer needed.
Rosie's House is a free music academy for youth in downtown Phoenix. Enrollment, attendance and family records lived in four tools. We connected DreamClass to Salesforce with a Make.com flow their staff can maintain, with no custom code. The stack above is illustrative.
Going from a blank slate to a finished tool is easy for us. We partner with you every step of the way to make sure we're capturing how your team works, and by the end we make sure you keep full ownership of the code we made together that runs your business. Here's what that looks like step by step:
4 to 6 weeks
Discovery
We interview the people who will use it, document how work happens today, and write a requirements document with scope options, a price range, and a build or don't-build recommendation.
The requirements document, yours either way.
6 to 20+ weeks
Build
Two-week sprints with a recorded demo at the end of each. You can change priorities every sprint.
Working software every two weeks.
About 4 weeks
Launch
Deployment, training for your team, and documentation for whoever maintains it next.
Source code in your repo, hosting in your account.
30 days, then retainer
Stabilize and stay
Thirty days of fixes included, then a retainer sized to how complex the tool is.
Admin access and deploy notes for any team.
Your toolLive
Records
Pending
Reports
RecordStatusOwner
Retainer: fixes and new features
Buy it, connect it, or build it?
Answer three questions. You'll see where most projects like yours land.
Example: Rosie's House answered yes, yes, no.
Where you'd likely land
Start with the questions
Pick an answer for each one. Not sure is a fine answer; that's what discovery is for.
Usually costs
Discovery from $2,500, credited toward any build
Build
When people outside your team use it, or the process is what sets you apart, owning the software is usually worth it.
Usually costs
Focused builds from $8,500. Discovery comes first.
Buy, then connect
Choose the product that fits, then connect it to the tools you already use so nobody copies data by hand.
That's what Rosie's House did: they chose DreamClass, built for music schools, and we connected it to their Salesforce with a Make.com flow. No custom code.
Usually costs
Software evaluation, plus integrations from $1,500
Buy
A product built for organizations like yours is usually cheaper and faster than building. We help you choose and set it up.
Usually costs
Software evaluation and setup, scoped on the first call
Connect what you have
The tools may be fine. The problem is the gaps between them. Integrations close those gaps.
Usually costs
Integrations from $1,500
Start with discovery
Not enough is clear yet. Four to six weeks of discovery ends with a written recommendation: build, buy, or neither.
More time spent on young musicians, and less on the paperwork
After speaking with their educators, staff, and a focus group of parents, we evaluated over 50 vendors to craft the perfect recommendation for Rosie's House. Our solution keeps them focused on educating the next generation of musicians instead of on their spreadsheets to this day, and they were given the knowledge they needed to keep it running year after year.
Marvin S.Program & Community Engagement Director, Rosie's House
How Magnolia builds for your business
We go through four rough stages designed to make sure that your investment is well-spent to achieve your goals, whether that's growing your team, increasing your customer retention, or improving your bandwidth and service reliability.
4 to 6 weeks
1. Discovery
We interview the people who will use it, document how work happens today, and write a requirements document with scope options, a price range, and a build or don't-build recommendation.
Your toolLive
Records
Pending
Reports
RecordStatusOwner
Retainer: fixes and new features
6 to 20+ weeks
2. Build
Two-week sprints with a recorded demo at the end of each. You can change priorities every sprint.
Your toolLive
Records
Pending
Reports
RecordStatusOwner
Retainer: fixes and new features
About 4 weeks
3. Launch
Deployment, training for your team, and documentation for whoever maintains it next.
Your toolLive
Records
Pending
Reports
RecordStatusOwner
Retainer: fixes and new features
30 days, then retainer
4. Stabilize and stay
Thirty days of fixes included, then a retainer sized to how complex the tool is.
Your toolLive
Records
Pending
Reports
RecordStatusOwner
Retainer: fixes and new features
Build, buy, or customize?
Ten questions we ask before any software decision. Answer them and see whether we would buy, customize or build, and why.
Member portals and dashboards from $15,000; larger platforms from $25,000. Discovery starts at $2,500 and is credited toward the build. Integrations from $1,500.
We say so, and we name the existing tool that fits. That's what happened with Rosie's House.
Can we change direction mid-build?
Small shifts each sprint are normal and free. Changing the core scope means a conversation about timeline and budget first.
What software do you use?
We typically reach for Ruby on Rails. Rails apps we've shipped are still running a decade later, and its conventions make handing the code to another team easy. We also really like how safe it feels to have AI agents work in it when needed as the framework lends itself to keeping coding agents compartmentalized to only where they're needed.
We don't only work with Ruby on Rails though... we've also built on Node, WordPress, Shopify, and others. We're kinda like code polyglots and build where the solution should be built, not just where we hang out most.
What happens when an integration breaks?
On a retainer, we fix it. For one-time projects, we quote the fix.
How long does an integration take?
A few days for a one-way sync with a standard API, a few weeks for custom authentication or two-way logic.
Tell us what's going on.
The first call is free and takes about 30 minutes. You talk to the people who would do the work, and we reply to every message within one business day.