The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Infrastructure as code for multi cloud
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Challenges
View all
Related posts
Hey, it’s been a while since my last update. I’ve been focused on a few projects behind the scenes, but I’m back with a major Weave milestone.
Weave helps professionals exchange time and expertise using Skill Hours instead of money.
My last update covered the invite application system. Since then, I’ve built:
Authentication: Secure account access with Firebase.
Onboarding: Guided profile and skill setup.
Profiles and portfolios: A place to showcase work, skills, and trust.
Member dashboard: A clear view of activity and ongoing work.
Admin dashboard: Tools for managing users and community health.
Skill Hour Ledger: Tracks every hour earned, spent, or transferred.
Marketplace: Members can publish requests and find collaborators.
Cloud infrastructure: Neon for data and storage, prepared for Cloudflare Workers.
Today’s milestone is the Exchange Workflow, the system connecting everything.
Members can now move from an accepted application into a dedicated workspace, communicate, share files, track milestones, submit deliverables, complete the exchange, transfer Skill Hours, and leave reviews.
The core Weave experience is finally taking shape, and I’m excited to share what comes next.
#BuildInPublic #WebDevelopment #ProductDesign #SaaS #NextJS #Contra
The milestone view makes the workflow feel tangible—especially the clear split between deliverables and activity. Nice product thinking in how you surface progress without adding noise.
Here’s how the system actually works.
A stranger sees your offer.
They click.
They become a lead.
But getting the lead is only the beginning.
The system now needs to know:
Who are they?
Where did they come from?
What are they interested in?
What have they done so far?
Then things start to branch.
If they respond → someone follows up.
If they book → the conversation changes.
If they don't respond → they enter another follow-up.
If they show buying intent → sales gets involved.
If they buy → they leave the sales journey and enter another one.
And all of this can happen without someone manually checking every lead.
That's the part of automation I find interesting.
It's not really about sending emails or SMS.
It's about building a system that reacts to what people do.
Traffic comes in.
Data gets collected.
Behaviour creates signals.
Signals trigger decisions.
Decisions create actions.
That's the dynamic behind a well-built CRM and automation system.
Hey, I built the entire application end to end. The real challenge inside the CRM automation is the perfect stages tagging along each stage if & else coordinations.
I built the entire wireframe. I can share with you.
Custom Software Development vs. Off-the-Shelf Solutions: When is a Tailored Approach Justified?
In practice, companies often try to adapt their business processes to the limitations of ready-made software. However, in the long term, it is more effective to tailor technology to business needs, rather than the other way around.
Custom software development means building an IT product to fit a company's specific requirements and workflows.
A tailored solution becomes necessary when a business faces the following challenges:
Specific processes. Unique operational algorithms that cannot be implemented using standard software.
Scaling limitations. Off-the-shelf software fails to handle growing loads, and vendor modifications are no longer cost-effective.
Security and autonomy. A need for full control over the architecture, source code, and data storage.
Complex integration. A requirement to combine fragmented IT systems into a single ecosystem.
Designing and building an IT product from scratch requires time and investment. However, the client ultimately gains independence from third-party licenses and a flexible tool ready for market changes.
I specialize in custom software development: designing architecture, writing clean code, and integrating systems. My goal is to create stable solutions that automate routine tasks and optimize internal processes.
I would love to discuss your experience in the comments: what limitations of off-the-shelf software have you encountered most often?
The honest line is usually integration count, not feature count. Off-the-shelf stays cheaper right up until the business needs its own data shape inside someone else's schema, and from there the cost moves into middleware and reconciliation jobs nobody budgeted. Custom is worth...