Rachel Keeney

Hi, I m Rachel and I m building affordable accounting and financial tools for construction. It s niche, but the needs are specific and the client base broad.

I ve created a pay application builder that creates AIA-style pay applications using the G702/G703 formats. The website doesn t capture and store data, rather the user downloads their pay applications as pdf s and the schedule of values as excel and re-uploads the file when they re ready to start the next month s pay application. The webpage grabs the project info, contractor logo, moves the completed work to previous columns, etc.

Hi everyone!

We're building CY Calculator to make construction and landscaping calculations easier, from cubic yard ofmeasurements to estimating materials like concrete, gravel, mulch, and soil.

Searched the sub for agent-driven dev workflows and came up pretty empty. I mean those setups where autonomous agents write code, test it, and basically deploy small apps with minimal hand-holding.

I run a few small automated tools myself, so I'd love to swap notes with people who are actually building this way.

Is anyone else playing with this? What frameworks or orchestration setups are you running for your coding agents? More importantly, how do you keep them from losing context or breaking things when the codebase gets bigger? What decisions are you letting the agent make completely on its own without reviewing first?