The long build
Three years to get one app right.
According to the founder, the original Circle app took nearly three years and development costs approaching five hundred thousand dollars. The seasons changed while the screens, workflows, permissions, and transaction logic kept evolving.
The money bought iteration, not certainty. Each version had to move closer to the real work without asking the customer to think like the developer.
Chapter three
Three years to get one app right.
A useful idea can be simple. Making it dependable is not.
The first version did not emerge complete. It never does. A developer can build exactly what was requested and still miss what the work feels like in a person's hands. A button can be correct and still appear at the wrong moment. A workflow can make sense in a diagram and become confusing when a real transaction changes direction.
So the founder kept returning to the problem. The app needed to know who belonged in a deal without exposing the wrong information. It needed to preserve evidence without making every ordinary exchange feel legalistic. It needed to carry detail without becoming a maze. Each correction made the product more useful, but each correction also consumed time and money.
Nearly three years is long enough for an idea to lose its shine. It is long enough for other people to ask whether the project will ever be finished. The founder continued because the problem was still there. Real-estate transactions still scattered their memory. People still needed a clearer way to finish the work and understand what had happened.
The long build
The founder and developer had to learn the same language.
The founder knew the transaction. The developer knew the code. Neither knowledge automatically translated into the other. A phrase that felt obvious in real estate could become ambiguous in a technical specification. A feature that looked complete in the software could miss the reason the founder asked for it.
The work moved through examples. What happens if the inspection changes the closing date? What happens if a vendor should see one task but not the rest of the deal? What happens if a person changes roles? What happens when an acknowledgment matters six months after everyone has forgotten the conversation?
Each example forced the two worlds closer together. The app improved when the code began to reflect the logic of the real work. The founder also learned that every apparently small change could touch permissions, records, screens, and behavior somewhere else. Three years were not spent polishing one idea. They were spent teaching a system how to carry responsibility.
Progress often appeared as a smaller sentence. A long explanation became one clear action. A complicated permission became a role the customer already understood. A technical edge case became a rule that matched the transaction. The product improved when the software stopped asking people to translate their lives into the language of the machine.
The long build
The cost was buying another chance to get it right.
By the founder's account, development costs approached five hundred thousand dollars before the app felt ready to carry a real transaction. That number can sound like a finish line. It was not. It was the accumulated price of trying again: another prototype, another correction, another conversation about how the work actually moved, another attempt to remove friction without removing responsibility.
The cost also created emotional weight. Walking away would not only mean losing money. It would mean admitting that a problem worth solving had defeated the effort to solve it. Continuing meant accepting that the next improvement might reveal the next weakness. There was no guarantee that one more round would be the final round.
Still, the product became real. The circle could hold a transaction. The people and their roles could remain visible. The tasks, messages, acknowledgments, documents, notes, contacts, and transcripts could belong to the same deal. The app had a job, and now it could do that job.
That should have been the moment when the founder finally turned toward the customer. Instead, he turned toward another machine.