PandaCodeGen / Custom software development & internal tools
Need a custom CRM, customer portal or a way to stop copying records between spreadsheets? We map the workflow, users and data, then scope a useful first release with the screens, automation, integrations and handover your team needs.
01 / See the work
Panda Patches connects commerce to order management. A Step Above Medical connects its course website to class operations. Explore the workflows and screens behind both live projects.
Project / Panda Patches CRM
Custom CRM development and workflow automation bring orders, production, payments and reporting into one system connected to the storefront.
Founder-affiliated work: Panda Patches shares an owner with PandaCodeGen. This is delivery evidence, not an independent client endorsement.
Project / A Step Above Medical
A medical training website and staff portal for class schedules, students, payments and certificates, with a Sanity editor for courses and locations.
Live independent client project. Screenshots were captured before launch and illustrate the interface.
02 / Review your site
Start with the records people retype, the approvals they wait for and the information customers need. We agree one complete workflow before expanding the application.
Which records are copied between spreadsheets, inboxes and tools, and who needs to see them?
Who can view, change or approve each step? The answer shapes the data model before a screen is designed.
We list hosting, integrations, licences and support alongside the build price.
We separate what must work on day one from features that need actual usage to justify them.
What the proposal resolves
Custom software development can mean a focused internal tool or a much larger product. The first proposal describes the job, users and boundaries.
Bring customer records, quotes and the team's next steps into a CRM shaped around your process. We agree the screens, roles, imports and connections first, and compare a new build with improving the system you already have.
Connect agreed steps such as a quote becoming an order, an invoice being sent or a delivery triggering follow-up. We define approvals, retries and what the team sees when an automated step fails.
For an operations dashboard or client portal, map the records, approvals and notifications people use today. Importing old data, connecting an existing system and changing staff permissions are separate decisions.
A subscription product adds login, account separation, billing and support workflows. We review who can access each customer's data and what happens when a payment or connection fails.
If an assistant would help, identify the approved guides and policies it may use, the sources it can show, and when a person takes over. Private information needs its own access rules.
The written terms identify repository access, third-party licences, intellectual-property transfer, documentation and who supports the release after launch.
Website SEO / Search and AI access
A custom CRM or portal should not expose customer records for search engines to read. If the project also has public service, product or help pages, we scope their search foundations separately from application access.
Need ongoing buyer research, page improvements and visibility reporting? AI search services are optional monthly work, scoped separately from the build. Search systems choose which pages they index or cite.
03 / Make the right call
We recommend the scope that addresses the evidence from your site and team, then put the work and boundaries in writing.
Fix a broken handoff or integration before replacing an entire system.
Scope a dashboard, portal or app around the people, records and decisions involved.
04 / From call to handover
Each stage creates something you can review. Your proposal names the deliverables and the point where you accept them.
Walk through a real task, the people involved and the information each one needs.
Write the screens, data, integrations, permissions and acceptance checks into the proposal.
Show working parts against real examples throughout the build.
Check roles, edge cases and connected systems, then transfer code, accounts and documentation as agreed.
05 / Published starting point
From $1,500
Starting point, not an instant quote.
Focused work can start at the published Starter price. A portal, SaaS product or complex integration is priced after requirements and dependencies are reviewed; the accepted proposal sets the final amount and dates.
Named users, workflows, data and integrations.
The working behaviours and test cases agreed before build.
Code, accounts and documentation transferred on handover.
After launch
The build is a one-off. These are the bills that continue, so add them up before you compare quotes.
Subscriptions it would replace
Your SaaS invoices and card statementHosting and database
For example Vercel Pro from $20 a month, plus your database providerMaintenance
Dependency updates and monitoring, agreed in the proposalManual work
The hours your team spends on spreadsheets and handoffsCompare the build and its running cost against the subscriptions and hours it replaces.
06 / Ownership & exports
PandaCodeGen hands over the code and design files created for your project, documentation and control of the production accounts. That applies to a portal, dashboard or web application as well as a website. Your written scope defines the delivery; third-party software and services keep their own licence terms.
Your project handover
You receive the project code and design files we create for you, plus documentation and control of the production accounts. If you then take a monthly support or care plan, that doesn't change: we keep sharing the code, documentation and accounts with you, so you always have your own copy. Third-party themes, plugins, services and assets remain under their own licence terms.
Yes. PandaCodeGen's published handover terms include the project code and design files we create for you, documentation and control of the production accounts. You keep your own copy if you choose ongoing care. Third-party software retains its own licence, so receiving project files does not transfer ownership of every tool used in the application.
Ending PandaCodeGen's optional support plan does not disable the application we build. Your team still needs to arrange hosting, renew any required third-party services and handle maintenance. Hosting moves to an account in your name on request or when the engagement ends. The handover and written proposal identify what needs ongoing attention.
The project code and design files we create for you.
Instructions handed over with the project files. If you take a care plan later, we keep sharing the documentation with you.
An editing walkthrough at handover, so your team can update the site. Every build that uses Sanity includes training on Sanity Studio and written documentation for it. On Starter, the content editor is set up, documented, and we train you on it.
Control of the production accounts. Hosting moves to your own account on request or when an engagement ends.
Your build keeps working without a PandaCodeGen care plan. Hosting and other provider services still need their own arrangements.
Your written proposal states the details for your project, including any third-party licences.
07 / Before you decide
These are starting answers. Project-specific details belong in the written proposal.
Keep exploring
All services ↗Related service
Backend development for CRMs and portals ↗