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
I built a mobile inventory and expiry tracking system to solve a real warehouse operations problem. Our Shopify workflow did not provide an efficient way to track product expiry dates, so I created a centralized Google Sheets inventory system and connected it to a mobile web app for barcode scanning. The app allows warehouse staff to quickly find products, check expiry dates and quantities, and update inventory while working on the warehouse floor.
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
Related posts
For Sienna Rhodes, I designed the homepage around one idea: the portfolio should come first.
Photography clients usually want to know one thing before they read about your process, your packages, or even who you are: Do I connect with your work?
So instead of opening with a traditional introduction, the homepage leads directly into the portfolio and lets the imagery make the first impression. The supporting copy and details come later, once the work has already created that initial connection.
I’m curious where other designers and photographers land on this. Do you prefer a portfolio-first homepage, or do you think the photographer’s story should come first?
Portfolio first, every time for photography. Nobody hires off a process paragraph, they hire because one image stopped them scrolling. The story matters, but it lands harder after the work has already made the case. That start here slider does the pitch by itself.
Obviously automated
Automated a manual Google Sheets → Slack workflow to eliminate repetitive data entry and give the team instant notifications.
Previously, new data had to be manually checked, processed, and shared across the team — slow and easy to miss. I built a Make.com scenario that:
Watches Google Sheets for new/updated rows
Processes and routes the data through a router based on conditions
Creates corresponding Trello cards for task tracking
Logs processed records back to Google Sheets
Sends real-time Slack notifications so the team is instantly updated
Result: What used to be manual checking and updating is now fully automated — saving hours weekly and removing room for human error.
Tools: Make.com, Google Sheets, Trello, Slack
wow love this