top of page

project wallets
category blueprint

projectwallets.com.png

automate contracts + cashflow
to build faster!

brief

who - project teams
how -
 use psychology & technology
what - to automate contracts + cashflow
where - instantly on blockchain

why -
 helping teams build faster!

project wallets

solving 4 project problems:

  • Owners want to build faster

  • Contractors want automation

  • Subs/Suppliers want to be paid faster

  • Lenders want to reduce risk

​​

1 team
projectwallets.com (3).png
1 team - Owner, Contractor, Subs/Suppliers, Lender (optional)​​​​​​​​​​​​​​​
Owner – primary stakeholder

primary benefit: faster delivery

biggest change: advanced funding schedule​​​​​​​​​​​​​​​

Contractor – project execution

primary benefit: team automation

biggest change: automation platform adoption​​​​​​​​​​​​​​​

​Sub/Supplier – labor and/or material (multiple)

primary benefit: paid faster

biggest change: invoices/payments on platform​​​​​​​​​​​​​​

​Lender (optional) – financial stakeholder

primary benefit: reduce risk

biggest change: advanced funding schedule​​​​​​​​​​​​​​

2 rails
projectwallets.com (3).png
​​​​​​​​​​​​​​​
2 rails - contracts + cashflow​​​​​​​​​​​​​​​​

​​​​​​​​​​​​​​

  1. Contractor codes the contract (by phase)

  2. Owner funds the contract (by phase)

  3. Contractor issues + funds subcontracts (w/invoices)

  4. Subs/Suppliers work + submit preset invoices

  5. Contractor approves invoices to pay Subs/Suppliers

  6. Owner approves completed phase to pay Contractor

      change orders modify contracts + cashflow (as needed)

 

The acrostic “automate” show the rails workflow.

​

contracts rail = the contract / subcontracts / invoices 
cashflow rail = project wallet / phases / user wallets​
3 steps
3 steps:​​​​​​​​​​​​​​
1. everyone gets a wallet
2. program the project wallet
3. fund / work / approve to pay​​​​​​​

​

everyone gets a wallet (aka - user wallets)

everyone is given a user wallet on the same blockchain so they can participate in the financial automation 

​​

program the project wallet

this is a single-use programmable blockchain wallet, owned / controlled by the Owner.

​

fund / work / approve to pay​​​​​​​​​​​​​​

projectwallets.com (2).png
4 parts
projectwallets.com (4).png
​4 parts - user wallets | project wallet | the contract | subcontracts

 

​​​​​​​​​using blockchain technology (wallets + smart contracts) we get 4 parts of a project wallet:

​

user wallets – blockchain wallet only

  • owned/funded/managed by the individual User

  • connected to an outside financial institution via on/off ramp

 

project wallet – blockchain wallet + smart contract

  • Owner owned/funded/managed

  • If/then – if there is a balance upon project completion / then it is sent to Owner

 

the contract (by phase) – blockchain wallet + smart contract

  • agreement between Owner + Contractor

    • scope – work to be performed

    • schedule – broken down by phase in sequential order

    • budget – each scope line has a value + OH&P

  • Contractor owned

  • Owner funded from project wallet (by phase)

  • scope of work (w/value) created when Contractor opened the wallet & approved by the Owner prior to funding

  • note: Sub/Supplier cannot see contract

  • if/then - if Owner approves the phase / then phase OH&P is sent to Contractor

  • modified by change order (as needed)

 

subcontract (w/invoices) – blockchain wallet + smart contract

  • agreement between Contractor + Sub/Supplier

  • Contractor owned

  • Contractor funded from contract

  • Invoices preset at the time of subcontract issue

  • note: Owner/Lender cannot see subcontract values – only progress

  • if/then - if Contractor approves invoice / then amount sent to Sub/Supplier

  • modified by change order (as needed)

why
projectwallets.com (4).png

project wallets change the way teams think / feel / act:​

​​

think

from: manual comes from a fixed mindset where everyone has to fight everyone to get their small piece of the limited resources available.  Rewards are subjective, benefiting the loudest (the squeaky wheel gets the grease) with “stick” motivation tactics trying to

 

to: automation leverages a growth mindset + cooperative game theory, where all parties work together to achieve exponential returns faster, while using less input.

 

feel

from: RI$K (real or perceived) hijacks the brain’s amygdala & shrinks neural pathways, so only rote memorization can be executed – so no new ideas will flow and problem-solving decisions will be reduced to only those that have been proven to work in the past. 

 

to: TRU$T from team automation releases oxytocin (known as the “trust” hormone)  enhancing feelings of safety & connection while activating reward circuits that reinforce positive social interactions and cooperative game play.   Creativity flows freely and problem-solving opportunities grow with exponentially beneficial outcomes.

 

act

from: FLOAT is the default action in the presence of RI$K (possibility of financial loss) as fear highjacks the brain’s amygdala - forces delay in both thought & action while reducing the number of solutions the brain can come up with.  “hurry up & wait”

 

to: FAST with the “trust hormone” oxytocin released, the team grows interpersonal confidence, and individual neural pathways expand - achieving peak performance in both action and creativity.  Peak performance, both personally and as a Team.

psychology
behavioral psychology  –  reward reinforcement

 

  1. clear goals (contracts)

  2. fast rewards (cashflow)

 

1.clear goals

The first necessary part of behavioral psychology’s reward reinforcement philosophy is to make sure that all parties can clearly identify a singular and clear goal to be accomplished.

 

clear goals = automate contracts

Using the smart contracts (if/then agreements) on blockchain, project wallets nest goals in the form of contracts + subcontracts so that all parties have clear goals.

 

  • the contract (by phase)

    • between the Owner + Contractor

    • including sequential scope of work + value to be done

    • broken down into phases (Contractor’s goals)

 

  • subcontracts (w/invoices)

    • nested inside phases

    • between the Contractor + Sub/Supplier

    • broken down with preset invoices (Sub/Suppliers goals)

​

nested goals = cooperative game play

by nesting the Contractor’s goal as the completion of a phase, their reward is now dependent on the Subs/Suppliers completing & closing all the subcontracts in that phase. 

 

​

2.fast rewards

The second part of reward reinforcement is the fast/immediate reward.  The longer the time delay from action to reward, the less effective and less likely to spur additional willful action.  

 

Fast rewards = automate cashflow

Since smart contracts are self-executing if/then agreements, all we needed was to ensure that the funds were available for instant release “approve to pay”.

 

Contractor reward = phase OH&P

  • goal – complete phase

  • work – subcontract & complete all contracted work

  • submit – Contractor submits completed phase

  • approval – Owner approves the phase

  • reward = phase OH&P (overhead & profit)

 

Sub/Supplier reward = invoice value

  • goal = preset invoice

  • work – scope of work in the subcontract

  • submit – Sub/Supplier submits completed invoice

  • approval – Contractor approves invoice

  • reward = invoice amount

technology
blockchain technology  –  value automation
​​

the cloud – was made to organize, store, & trade DATA

blockchain – was made to organize, store, & trade VALUE

 

blockchain was built to organize, trade, and automate the exchange of digital assets safely & securely between parties.  A decentralized system with immutable ledgers and real-time access for all parties makes it the perfect place to use a combination of holding containers (wallets) and self-executing programs (smart contracts) to build an automation platform for contracts + cashflow.

 

blockchain parts

  1. smart contracts (if/then agreements)

  2. stablecoins (digital value)

  3. wallets (hold stablecoin)

© 2025 project wallets - all rights reserved

bottom of page